← Home

jsonwebtoken

JSON Web Token implementation (symmetric and asymmetric)

4
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

charlesreadavid.renaud.oktajulien.wollscheidjavierquevedo

Keywords

jwt

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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

Versions (showing 4 of 4)

Version Deps Published
9.0.3 10 / 8
9.0.2 10 / 9
9.0.1 4 / 9
9.0.0 4 / 9

v9.0.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien.wollscheid → jake.lacey (on 2023-07-05, known maintainer) provenance

This version was published by a different npm account (jake.lacey) than the most recent previously approved version (julien.wollscheid) on 2023-07-05, but jake.lacey is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.