@polkadot/util-triehash
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 | no-provenance | AI (provenance): Package is ~8 years old, published long before Sigstore provenance was available on npm. This is expected for the entire polkadot-js ecosystem of that era. | ai | |
| npm-metadata | url-dep:rlp | AI (npm-metadata): The GitHub fork jacogr/rlp is maintained by the same trusted publisher (jacogr) who owns this package. Risk of malicious substitution is low given author controls both. | ai | |
| dependencies | unvetted-dep:@polkadot/util-rlp | AI (dependencies): @polkadot/util-rlp is a sibling package from the same polkadot-js/util monorepo, published by the same trusted maintainer (jacogr). Not a real risk. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.24.9 | 4 / 0 | |
| 0.24.8 | 4 / 0 | |
| 0.24.7 | 4 / 0 | |
| 0.24.6 | 4 / 0 | |
| 0.24.5 | 4 / 0 | |
| 0.24.4 | 4 / 0 | |
| 0.24.3 | 4 / 0 | |
| 0.24.2 | 4 / 0 | |
| 0.24.1 | 4 / 0 | |
| 0.23.2 | 4 / 0 | |
| 0.23.1 | 4 / 0 | |
| 0.22.11 | 4 / 0 | |
| 0.22.10 | 4 / 0 | |
| 0.22.9 | 4 / 0 | |
| 0.22.8 | 4 / 0 | |
| 0.22.7 | 4 / 0 | |
| 0.22.6 | 4 / 0 | |
| 0.22.5 | 4 / 0 | |
| 0.22.4 | 4 / 0 | |
| 0.22.3 | 4 / 0 | |
| 0.22.2 | 4 / 0 | |
| 0.22.1 | 4 / 0 | |
| 0.21.3 | 4 / 0 | |
| 0.21.2 | 4 / 0 | |
| 0.21.1 | 4 / 0 | |
| 0.20.5 | 4 / 0 | |
| 0.20.4 | 4 / 0 | |
| 0.20.3 | 4 / 0 | |
| 0.19.9 | 4 / 0 | |
| 0.19.8 | 4 / 0 | |
| 0.19.7 | 4 / 0 | |
| 0.19.6 | 4 / 0 | |
| 0.19.5 | 4 / 0 | |
| 0.19.4 | 4 / 0 | |
| 0.19.3 | 4 / 0 | |
| 0.19.2 | 4 / 0 | |
| 0.19.1 | 4 / 0 | |
| 0.18.6 | 4 / 0 | |
| 0.18.5 | 4 / 0 | |
| 0.18.4 | 4 / 0 | |
| 0.18.3 | 4 / 0 | |
| 0.18.2 | 4 / 0 | |
| 0.18.1 | 4 / 0 | |
| 0.17.4 | 4 / 0 | |
| 0.17.3 | 4 / 0 | |
| 0.17.2 | 4 / 0 | |
| 0.17.1 | 4 / 0 | |
| 0.16.6 | 4 / 0 | |
| 0.16.5 | 4 / 0 | |
| 0.16.4 | 4 / 0 | |
| 0.16.3 | 4 / 0 |
v0.24.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.