cacheable
High Performance Layer 1 / Layer 2 Caching with Keyv Storage
Supply chain provenance
Status for the latest visible version.
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): Transition from personal account to GitHub Actions CI/CD publishing with SLSA provenance; expected pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 8.5M downloads; dormancy followed by CI-published release is normal maintenance cadence. | ai | |
| dependencies | unvetted-dep:qified | AI (dependencies): qified is a first-party dependency from the same publisher (jaredwray) within the cacheable monorepo ecosystem; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@cacheable/utils | AI (dependencies): @cacheable/utils is a first-party scoped package from the same jaredwray/cacheable monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@cacheable/memory | AI (dependencies): @cacheable/memory is a first-party scoped package from the same jaredwray/cacheable monorepo; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 5 / 6 | |
| 2.3.5 | 5 / 6 | |
| 2.3.4 | 5 / 6 | |
| 2.3.3 | 5 / 9 | |
| 2.3.2 | 5 / 12 | |
| 2.3.1 | 5 / 12 | |
| 2.3.0 | 5 / 12 | |
| 2.2.0 | 5 / 12 | |
| 2.1.1 | 6 / 12 | |
| 2.1.0 | 6 / 12 | |
| 2.0.3 | 5 / 11 | |
| 2.0.2 | 5 / 11 | |
| 2.0.1 | 5 / 11 | |
| 2.0.0 | 5 / 11 |
v2.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.