did-jwt
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:did-resolver | AI (dependencies): did-resolver is the canonical DIF DID resolver library and a natural, expected dependency for did-jwt. Not a risk signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established DIF package with 157 versions; lack of Sigstore provenance is common and not a meaningful risk for this well-known library. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.0.18 | 9 / 38 | |
| 8.0.17 | 9 / 38 | |
| 8.0.16 | 9 / 38 | |
| 8.0.15 | 9 / 38 |
v8.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.