cacheable-request
Wrap native HTTP requests with RFC compliant cache support
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transfer to jaredwray's cacheable monorepo; jaredwray is established maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jaredwray now maintains the cacheable monorepo; stable going forward. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): mimic-response and @types/http-cache-semantics are standard deps for this package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Mature, high-download package predating Sigstore provenance adoption; absence is expected and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/http-cache-semantics | AI (phantom-deps): Intentionally placed in dependencies (not devDependencies) to expose TypeScript types to consumers, as documented in package.json's dependenciesComments. This is a stable, legitimate pattern for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 13.0.19 | 7 / 10 | |
| 13.0.18 | 7 / 15 | |
| 13.0.17 | 7 / 15 | |
| 13.0.16 | 7 / 15 | |
| 13.0.15 | 7 / 15 | |
| 13.0.14 | 7 / 15 | |
| 13.0.13 | 7 / 15 | |
| 13.0.12 | 7 / 15 | |
| 13.0.11 | 7 / 15 | |
| 13.0.10 | 7 / 15 | |
| 13.0.9 | 7 / 15 | |
| 13.0.8 | 7 / 15 | |
| 13.0.7 | 7 / 14 | |
| 13.0.6 | 7 / 14 | |
| 13.0.4 | 7 / 15 | |
| 13.0.0 | 7 / 14 | |
| 7.0.4 | 7 / 11 | |
| 7.0.2 | 7 / 11 |
v13.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2025-03-03. 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.
v13.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2024-10-21. 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.
v7.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-07. This could indicate a legitimate maintainer transition or an account compromise.