@azure-tools/jsonschemanpm
- latest 1.3.1
- last known licence MIT
- stars 4,794
- assessment attempted 15 days ago
- registry 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
18
Open issues
21
Unanswered
13
Contributors
6
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=12.0.0. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog 15/15 done; Copper 4/4 done; Nickel (due 2021-12-31) 11/11 done; [2022] January (due 2022-01-07) 6/6 done; [2022] February (due 2022-02-04). Source: the repository's milestones.
- OpenSSF Scorecard — 5.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 15 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-14 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@azure-tools/jsonschema)Watch it
Get told when @azure-tools/jsonschema 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.