@cacheable/memory
High Performance In-Memory Cache for Node.js
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cacheable/memoize | AI (dependencies): @cacheable/memoize is a first-party dependency from the same publisher (jaredwray) and monorepo (cacheable). Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@keyv/bigmap | AI (dependencies): @keyv/bigmap is a sibling package in the same cacheable monorepo by the same trusted publisher (jaredwray); unvetted status reflects pipeline ordering, not a real risk. | ai | |
| dependencies | unvetted-dep:@cacheable/utils | AI (dependencies): @cacheable/utils is a sibling package in the same cacheable monorepo by the same trusted publisher (jaredwray); unvetted status reflects pipeline ordering, not a real risk. | ai | |
| phantom-deps | phantom-dep:@keyv/bigmap | AI (phantom-deps): @keyv/bigmap is a declared runtime dependency in package.json from the same cacheable ecosystem; phantom detection is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): jaredwray's packages consistently lack provenance attestation; this is a known pattern for this publisher and not a security concern given their clean track record. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.9 | 4 / 2 | |
| 2.0.8 | 4 / 5 | |
| 2.0.7 | 4 / 8 | |
| 2.0.6 | 4 / 8 | |
| 2.0.5 | 4 / 8 | |
| 2.0.4 | 4 / 8 | |
| 2.0.3 | 5 / 8 | |
| 2.0.2 | 5 / 9 | |
| 2.0.1 | 5 / 9 | |
| 2.0.0 | 5 / 9 | |
| 1.0.1 | 5 / 9 | |
| 1.0.0 | 5 / 12 |
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.
v1.0.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.
v1.0.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.