Is jsonwebtoken healthy, maintained, and safe?
No — jsonwebtoken carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The verdict
On the OSPulse health scale, jsonwebtoken lands at 10/100 — critical risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — jsonwebtoken carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The newest release dates to 4 December 2025, 235 days back — a gap long enough to suggest the pace is slowing. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 4 known advisories for jsonwebtoken, including 1 critical and 1 high. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
The safest reading is to replace, fork, or tightly pin jsonwebtoken and stop taking on new exposure to it. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (4)
jsonwebtoken unrestricted key type could lead to legacy keys usage
Verification Bypass in jsonwebtoken
jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC
jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()
Key facts
- Latest version
- v9.0.3
- Last release
- 4 December 2025 (235 days ago)
- Total releases
- 82
- First release
- 1 July 2013
- Package age
- 13.1 years
- Maintainers
- 1
- Known advisories
- 4
- Confidence
- High
Frequently asked
Is jsonwebtoken still maintained?
Partly — the most recent release was 4 December 2025 (235 days ago), so maintenance has slowed but not fully stopped.
Does jsonwebtoken have known security vulnerabilities?
Yes — OSV lists 4 advisories for jsonwebtoken, including 1 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is jsonwebtoken safe to use?
No — jsonwebtoken carries 1 unpatched critical advisory and should not be adopted without a remediation plan. OSPulse rates it 10/100 (critical risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
jsonwebtoken is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.