@ethereumjs/binarytree
Implementation of binary trees as used in Ethereum.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ethereumjs/rlp | AI (dependencies): Sibling package from the same ethereumjs-monorepo; expected dependency for this package, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ethereumjs/util | AI (dependencies): Sibling package from the same ethereumjs-monorepo; expected dependency for this package, not a risk signal. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.1.2 | 5 / 1 | |
| 10.1.1 | 5 / 1 | |
| 10.1.0 | 6 / 1 | |
| 10.0.0 | 6 / 0 |
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.