github.com/projectcalico/calico-containersGo
- latest v2.0.7+incompatible
- licence Apache-2.0
- stars 7,395
- assessment attempted today
- GitHub evidence observed today
- 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 →Moved
The registry still points at projectcalico/calico-containers, which is archived with a note saying development moved to projectcalico/calico. The verdict above is about the new home.
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
- Security policy — published. Source: the repository.
- Open milestones — Calico v3.30.8 23/23 done; Calico v3.34.0 424/588 done; Calico v3.31.8 41/46 done; Calico v3.32.3 68/83 done; Calico v3.33.1 28/33 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.2 / 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 today; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-19 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/go/github.com/projectcalico/calico-containers)Watch it
Get told when github.com/projectcalico/calico-containers 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.