← Home

@nxtedition/cache

npm

A two-tier async cache with SQLite persistence, in-memory pseudo-LRU, stale-while-revalidate, cross-thread deduplication via `SharedArrayBuffer`, and automatic request coalescing.

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

qtodennxtadminronaggulpfniklaspanderssonolzzonhaasngnzphillipjacobdwyfldeadbeef84tobiasandersen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@nxtedition/trace AI (dependencies): First-party @nxtedition scoped package from same org, not third-party unvetted code. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is a first-party sibling package, low risk profile. ai

Versions (showing 51 of 67)

View all versions
Version Deps Published
3.0.1 3 / 3
3.0.0 3 / 3
2.2.4 3 / 5
2.2.3 3 / 5
2.2.2 3 / 5
2.2.1 3 / 5
2.2.0 3 / 5
2.1.37 2 / 5
2.1.36 2 / 5
2.1.35 2 / 5
2.1.34 2 / 5
2.1.33 2 / 5
2.1.32 2 / 5
2.1.31 2 / 5
2.1.30 2 / 5
2.1.29 2 / 5
2.1.28 2 / 5
2.1.27 2 / 5
2.1.26 2 / 5
2.1.25 2 / 5
2.1.24 2 / 5
2.1.23 2 / 5
2.1.22 2 / 5
2.1.21 2 / 5
2.1.20 2 / 5
2.1.19 2 / 5
2.1.18 2 / 5
2.1.17 2 / 5
2.1.16 2 / 5
2.1.15 2 / 5
2.1.14 2 / 5
2.1.13 2 / 6
2.1.12 2 / 6
2.1.11 2 / 6
2.1.10 0 / 6
2.1.9 0 / 6
2.1.8 0 / 6
2.1.7 0 / 6
2.1.6 0 / 6
2.1.5 0 / 6
2.1.4 0 / 6
2.1.3 0 / 6
2.1.2 0 / 6
2.1.1 0 / 6
2.1.0 0 / 6
2.0.7 0 / 6
2.0.6 0 / 6
2.0.5 0 / 6
2.0.4 0 / 6
2.0.3 0 / 6
2.0.2 0 / 6

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.2.4

1 finding
LOW No provenance attestation provenance

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

v2.2.3

1 finding
LOW No provenance attestation provenance

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

v2.2.2

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.37

1 finding
LOW No provenance attestation provenance

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

v2.1.36

1 finding
LOW No provenance attestation provenance

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

v2.1.35

1 finding
LOW No provenance attestation provenance

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

v2.1.34

1 finding
LOW No provenance attestation provenance

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

v2.1.33

1 finding
LOW No provenance attestation provenance

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

v2.1.32

1 finding
LOW No provenance attestation provenance

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

v2.0.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ronag → gnz (on 2026-03-13, known maintainer) provenance

This version was published by a different npm account (gnz) than the most recent previously approved version (ronag) on 2026-03-13, but gnz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.