catbox
Multi-strategy object caching service
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): The hueniverse→kanongil transition in 2018 is a known, legitimate hapi.js ecosystem maintainer handoff. kanongil has a strong track record and this is stable for all versions of this package. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 10.0.6 | 3 / 2 | |
| 10.0.5 | 3 / 2 | |
| 10.0.4 | 3 / 2 | |
| 10.0.3 | 3 / 2 | |
| 10.0.2 | 4 / 2 | |
| 10.0.1 | 3 / 2 | |
| 10.0.0 | 3 / 2 | |
| 9.0.0 | 3 / 2 | |
| 8.0.1 | 3 / 2 | |
| 8.0.0 | 3 / 2 | |
| 7.2.1 | 3 / 2 | |
| 7.1.5 | 3 / 2 | |
| 7.1.4 | 3 / 2 | |
| 7.1.3 | 3 / 2 | |
| 7.1.2 | 3 / 2 | |
| 7.1.1 | 3 / 2 | |
| 7.1.0 | 3 / 2 | |
| 7.0.0 | 3 / 2 | |
| 6.0.0 | 3 / 2 | |
| 4.3.0 | 3 / 2 | |
| 4.2.2 | 3 / 2 | |
| 4.2.1 | 3 / 2 | |
| 4.2.0 | 3 / 2 | |
| 4.1.0 | 3 / 2 | |
| 4.0.3 | 3 / 1 | |
| 4.0.2 | 3 / 1 | |
| 4.0.1 | 3 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.4.3 | 2 / 1 | |
| 3.4.2 | 2 / 1 | |
| 3.4.1 | 2 / 1 | |
| 3.4.0 | 2 / 1 | |
| 3.3.0 | 2 / 1 | |
| 3.2.0 | 2 / 1 | |
| 3.1.0 | 2 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.2.1 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 1.2.0 | 1 / 5 | |
| 1.1.3 | 1 / 4 | |
| 1.1.2 | 1 / 4 | |
| 1.1.1 | 1 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.0 | 1 / 3 | |
| 0.6.2 | 1 / 3 | |
| 0.6.1 | 1 / 3 | |
| 0.6.0 | 1 / 3 | |
| 0.5.2 | 1 / 3 | |
| 0.5.1 | 1 / 3 | |
| 0.5.0 | 1 / 3 |
v10.0.6
2 findingsThis version was published by a different npm account than previous versions on 2018-12-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.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-17. This could indicate a legitimate maintainer transition or an account compromise.