@keyv/redis
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redux | AI (typosquat): @keyv/redis is a scoped package in the well-known keyv monorepo; Levenshtein match against 'redux' is a false positive with no semantic or visual similarity. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.1.6 | 3 / 8 | |
| 5.1.5 | 3 / 8 | |
| 5.1.4 | 3 / 8 | |
| 5.1.3 | 3 / 8 | |
| 5.1.2 | 3 / 8 | |
| 5.1.1 | 3 / 8 | |
| 5.1.0 | 3 / 8 | |
| 5.0.0 | 3 / 8 |
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.