github.com/pivotalservices/cf-mgmtGo
- latest v1.0.106
- licence Apache-2.0
- stars 121
- assessment attempted 9 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Open milestones — 1.0.37 6/6 done; 1.0.38 2/2 done; v1.0.86; v1.0.87 1/1 done; v1.0.80 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 9 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-09 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/go/github.com/pivotalservices/cf-mgmt)Watch it
Get told when github.com/pivotalservices/cf-mgmt changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.