session-cache
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change jonschlinkert→doowb occurred in 2014; doowb is the documented author in package.json and a well-established npm publisher. Legitimate historical transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): doowb added as maintainer in 2014 matches the package author field; well-established publisher with strong track record. No ongoing risk. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4182 days old, predating Sigstore provenance. No provenance is expected and not a risk signal for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 1 / 2 | |
| 0.1.3 | 1 / 2 | |
| 0.1.2 | 1 / 2 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2014-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.