keyv
Simple key-value storage with support for multiple backends
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from lukechilds to jaredwray, who now owns the GitHub org and is the recognized maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jaredwray is the legitimate new maintainer of the keyv ecosystem; this transfer is publicly documented. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy corresponds to the maintainer transition period; jaredwray resumed active development. | ai | |
| provenance | missing-githead | AI (provenance): Expected when publish environment changed during maintainer transition; not a security signal for keyv. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load a storage adapter from a controlled lookup map keyed by URI scheme — a standard plugin pattern for this multi-backend library, not arbitrary code execution. | ai | |
| dependencies | unvetted-dep:json-buffer | AI (dependencies): json-buffer is a small, well-known serialization utility that is a natural and long-standing dependency for keyv's serialization needs. No advisories present. | ai | |
| dependencies | unvetted-dep:@keyv/serialize | AI (dependencies): @keyv/serialize is a first-party dependency from the same jaredwray/@keyv organization; it is a stable, expected dependency for this package. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 1 / 16 | |
| 5.5.5 | 1 / 14 | |
| 5.5.4 | 1 / 14 | |
| 5.5.3 | 1 / 14 | |
| 5.5.2 | 1 / 14 | |
| 5.5.1 | 1 / 14 | |
| 5.5.0 | 1 / 14 | |
| 5.4.0 | 1 / 14 | |
| 5.3.4 | 1 / 14 | |
| 5.3.3 | 1 / 14 | |
| 5.3.2 | 1 / 14 | |
| 5.3.1 | 1 / 14 | |
| 5.3.0 | 1 / 14 | |
| 5.2.3 | 1 / 10 | |
| 5.2.2 | 1 / 10 | |
| 5.2.1 | 1 / 10 | |
| 5.2.0 | 1 / 10 | |
| 5.1.3 | 1 / 10 | |
| 5.1.2 | 1 / 10 | |
| 5.1.1 | 1 / 10 | |
| 5.1.0 | 1 / 5 | |
| 5.0.3 | 1 / 5 | |
| 5.0.2 | 1 / 5 | |
| 5.0.1 | 1 / 4 | |
| 5.0.0 | 1 / 4 | |
| 4.5.4 | 1 / 6 | |
| 4.5.3 | 1 / 6 | |
| 4.5.2 | 1 / 11 | |
| 4.5.1 | 1 / 11 | |
| 4.5.0 | 1 / 11 | |
| 4.4.1 | 2 / 11 | |
| 4.4.0 | 2 / 11 | |
| 4.3.3 | 2 / 11 | |
| 4.3.2 | 2 / 10 | |
| 4.3.1 | 2 / 10 | |
| 4.3.0 | 2 / 10 | |
| 4.2.9 | 2 / 10 | |
| 4.2.8 | 2 / 10 | |
| 4.2.7 | 2 / 10 | |
| 4.2.6 | 2 / 10 | |
| 4.2.5 | 2 / 10 | |
| 4.2.2 | 2 / 10 | |
| 4.2.1 | 2 / 10 | |
| 4.2.0 | 2 / 11 | |
| 4.1.1 | 1 / 9 | |
| 4.1.0 | 1 / 9 | |
| 4.0.5 | 1 / 13 | |
| 4.0.4 | 1 / 13 | |
| 4.0.3 | 1 / 13 | |
| 4.0.2 | 1 / 13 | |
| 4.0.1 | 1 / 13 | |
| 4.0.0 | 1 / 13 |
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-05-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-04-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-02-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-02-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jaredwray.
This version was published by a different npm account than previous versions on 2022-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.