← Home

@checkstack/cache-memory-backend

41
Versions
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Scoped internal package; missing description is typical for monorepo libraries. ai
bogus-package bogus-package AI (bogus-package): Scoped internal package; metadata signals reflect monorepo pattern, not malice. ai
dependencies unvetted-dep:@checkstack/cache-api AI (dependencies): Internal @checkstack monorepo dependency; consistent with package's ecosystem context. ai
dependencies unvetted-dep:@checkstack/backend-api AI (dependencies): Internal @checkstack monorepo dependency; consistent with package's ecosystem context. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. ai

Versions (showing 41 of 41)

Version Deps Published
0.3.35 5 / 3
0.3.34 5 / 3
0.3.33 5 / 3
0.3.32 5 / 3
0.3.31 5 / 3
0.3.30 5 / 3
0.3.29 5 / 3
0.3.28 5 / 3
0.3.27 5 / 3
0.3.26 5 / 3
0.3.25 5 / 3
0.3.24 5 / 3
0.3.23 5 / 3
0.3.22 5 / 3
0.3.21 5 / 3
0.3.20 5 / 3
0.3.19 5 / 3
0.3.18 5 / 3
0.3.17 5 / 3
0.3.16 5 / 3
0.3.15 5 / 3
0.3.14 5 / 3
0.3.13 5 / 3
0.3.12 5 / 3
0.3.11 5 / 3
0.3.10 5 / 3
0.3.9 5 / 3
0.3.8 5 / 3
0.3.7 5 / 3
0.3.6 5 / 3
0.3.5 5 / 3
0.3.4 5 / 3
0.3.3 5 / 3
0.3.2 5 / 3
0.3.1 5 / 3
0.3.0 5 / 3
0.2.4 5 / 3
0.2.3 5 / 3
0.2.2 5 / 3
0.2.1 5 / 3
0.2.0 5 / 3

v0.3.35

1 finding
INFO No provenance attestation provenance

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

v0.3.34

1 finding
INFO No provenance attestation provenance

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

v0.3.33

1 finding
INFO No provenance attestation provenance

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

v0.3.32

1 finding
INFO No provenance attestation provenance

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

v0.3.31

1 finding
INFO No provenance attestation provenance

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

v0.3.30

1 finding
INFO No provenance attestation provenance

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

v0.3.29

1 finding
INFO No provenance attestation provenance

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

v0.3.28

1 finding
INFO No provenance attestation provenance

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

v0.3.27

1 finding
INFO No provenance attestation provenance

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

v0.3.26

1 finding
INFO No provenance attestation provenance

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

v0.3.25

1 finding
INFO No provenance attestation provenance

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

v0.3.24

1 finding
INFO No provenance attestation provenance

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

v0.3.23

1 finding
INFO No provenance attestation provenance

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