← Home

jwt-service

npm Repository Homepage
3
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

nfroidure

Keywords

jwtknifecycle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Trusted long-standing publisher with 95 approved packages; no suspicious changes in this version. ai
phantom-deps phantom-dep:@types/ms AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not direct imports; stable false positive. ai
phantom-deps phantom-dep:@types/jsonwebtoken AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not direct imports; stable false positive. ai

Versions (showing 3 of 3)

Version Deps Published
12.0.2 7 / 20
12.0.1 7 / 20
12.0.0 7 / 20

v12.0.2

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.

v12.0.1

1 finding
LOW No provenance attestation provenance

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

v12.0.0

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.