@ngtools/json-schemanpm
- latest 1.1.0
- licence MIT
- stars 27,023
- checked 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 →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
100
Open issues
242
Unanswered
39
Contributors
5
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >= 4.1.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — needsTriage 774/852 done; Backlog 1337/1369 done; v22 candidates; v20 Candidates (due 2025-05-21) 5/5 done; v21 candidates (due 2025-11-19). Source: the repository's milestones.
- OpenSSF Scorecard — 7.5 / 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-09-17 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@ngtools/json-schema)Watch it
Get told when @ngtools/json-schema 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.