← Home

cacheable

npm Repository Homepage

High Performance Layer 1 / Layer 2 Caching with Keyv Storage

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jaredwray

Keywords

cacheablehigh performancelayer 1 cachinglayer 2 cachingdistributed cachingKeyv storage enginememory cachingLRU cacheexpirationCacheableMemoryoffline supportdistributed syncsecondary storeprimary storenon-blocking operationscache statisticslayered cachingfault tolerantscalable cachein-memory cachedistributed cachelruSizelrumulti-tier cache

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 13 of 13)

Version Deps Published
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.3.5

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

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.

v2.3.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.

v2.2.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.

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.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.