jsonwebtoken
JSON Web Token implementation (symmetric and asymmetric)
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
charlesreadavid.renaud.oktajulien.wollscheidjavierquevedo
Keywords
jwt
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:jws | AI (dependencies): jws is the expected core dependency of jsonwebtoken for JSON Web Signature operations; same auth0 ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): jsonwebtoken is a well-established auth0 package; lack of Sigstore provenance is not a material risk for this publisher. | ai |
v9.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.