hive-keychain-commons
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Fires on standard SHA256 hex encoding in crypto.utils.js; not obfuscation, stable pattern for this crypto library. | ai | |
| phantom-deps | phantom-dep:secp256k1 | AI (phantom-deps): secp256k1 is a declared runtime dep used via native bindings; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.14.0 | 9 / 9 | |
| 1.13.3 | 9 / 9 | |
| 1.13.2 | 9 / 9 | |
| 1.13.1 | 9 / 9 | |
| 1.13.0 | 9 / 9 | |
| 1.12.0 | 9 / 9 | |
| 1.11.0 | 9 / 9 | |
| 1.10.3 | 9 / 9 | |
| 1.10.2 | 9 / 9 | |
| 1.10.1 | 9 / 9 | |
| 1.10.0 | 9 / 9 | |
| 1.9.9 | 9 / 9 | |
| 1.9.8 | 9 / 9 | |
| 1.9.7 | 9 / 9 | |
| 1.9.6 | 9 / 9 | |
| 1.9.5 | 9 / 9 | |
| 1.9.4 | 9 / 9 | |
| 1.9.3 | 9 / 9 | |
| 1.9.2 | 9 / 9 | |
| 1.9.1 | 9 / 9 | |
| 1.9.0 | 9 / 9 |
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.