@curity/jwt-validationnpm
- latest 1.2.0
- last known licence UNLICENSED
- assessment attempted 19 days ago
- registry checked 16 days ago
- registry ↗
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
—
Open issues
—
Unanswered
—
Contributors
—
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 8. Source: the registry.
Third-party facts checked 19 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-21 | first verdict: unknown |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-09-21 | Apache-2.0 → Proprietary (1.2.0) | critical |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@curity/jwt-validation)Watch it
Get told when @curity/jwt-validation 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.