jwt-simple
1
Versions
—
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
hokaccha
Keywords
jwtencodedecode
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is the core, expected functionality of a JWT library. The flagged code is the standard base64url decode implementation required by the JWT specification — not a malicious payload. | ai | |
| provenance | no-provenance | AI (provenance): jwt-simple is a mature, well-established package. Lack of Sigstore provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.5.6 | 0 / 3 |
v0.5.6
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.