← Home

@keyvhq/redis

npm Repository Homepage
16
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

kikobeatsjytesh

Keywords

adaptercachekeykeyvredisstoragestorettlvalue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): No code/dep changes in this version; long-dormant monorepo package resuming maintenance is plausible given publisher track record. ai
typosquat typosquat.levenshtein:redux AI (typosquat): Scoped Keyv Redis adapter; name similarity to redux is coincidental, not impersonation. ai

Versions (showing 16 of 16)

Version Deps Published
2.2.3 1 / 7
2.1.17 1 / 7
2.1.15 1 / 7
2.1.13 1 / 7
2.1.12 1 / 7
2.1.11 1 / 7
2.1.10 1 / 7
2.1.8 1 / 7
2.1.7 1 / 7
2.1.5 1 / 7
2.1.4 1 / 7
2.1.3 1 / 7
2.1.2 2 / 7
2.1.1 2 / 7
2.1.0 2 / 7
2.0.0 2 / 7

v2.1.8

1 finding
LOW No provenance attestation provenance

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

v2.1.7

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

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

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

1 finding
LOW No provenance attestation provenance

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

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