@peculiar/json-schemanpm
- latest 3.0.0
- last known licence MIT
- stars 3
- assessment attempted 27 days ago
- GitHub evidence observed 27 days ago
- registry checked 27 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 →Came back
After 6 years without a release, @peculiar/json-schema published 3.0.0 on 2026-10-16.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 3 checks
What the project says about itself
- Build provenance — the latest release, 3.0.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node ^20.19.0 || >=22.12.0. Source: the registry.
- Publishers on the registry — 7. Source: the registry.
- OpenSSF Scorecard — 2 / 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 27 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-17 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@peculiar/json-schema)
Watch it
Get told when @peculiar/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.