@castlefinance/anchornpm
- latest 0.24.2-patch1
- last known licence (MIT OR Apache-2.0)
- stars 5,166
- assessment attempted today
- GitHub evidence observed today
- registry checked 10 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 5 checks
Commits 90d
100
Open issues
30
Unanswered
4
Contributors
40
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=11. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — v2.0.0-rc.3 54/54 done; v1.2.3 47/49 done; v2.0.0-rc.4 (due 2026-11-16) 2/2 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.9 / 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-11-08 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@castlefinance/anchor)Watch it
Get told when @castlefinance/anchor 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.