ts-nodenpm
- latest 10.9.2
- last known licence MIT
- stars 13,116
- assessment attempted 13 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
197
Unanswered
82
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — next 3/16 done; 10.10.0 or 11.0.0 (TODO combine with v11 milestone) 1/8 done; v11 1/5 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.6 / 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 13 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-10 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/ts-node)Watch it
Get told when ts-node 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.