@valibot/to-json-schemanpm
- latest 1.8.0
- licence MIT
- stars 9,001
- checked 5 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 2 checks
Commits 90d
62
Open issues
85
Unanswered
9
Contributors
40
What the project says about itself
- Build provenance — the latest release, 1.8.0, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — v2 1/15 done; v1.6 14/37 done; v1.6 (to-json-schema) 4/6 done. Source: the repository's milestones.
Third-party facts checked 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-09-13 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@valibot/to-json-schema)Watch it
Get told when @valibot/to-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.