victory-cursor-containernpm
- latest 37.3.6
- licence MIT
- stars 11,240
- assessment attempted yesterday
- GitHub evidence observed 2 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.
Commits 90d
0
Open issues
84
Unanswered
26
Contributors
2
What the project says about itself
- Build provenance — the latest release, 37.3.6, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=18.0.0. Source: the registry.
- Publishers on the registry — 9. Source: the registry.
- Open milestones — Replace class inheritance with component composition 1/2 done; Improve bundle size 4/5 done; Convert Victory to Typescript 6/6 done; Victory Turbo 3/5 done; Monrepo infrastructure 8/10 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.1 / 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 yesterday; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-18 | first verdict: coasting |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/victory-cursor-container)Watch it
Get told when victory-cursor-container 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.