@ethereumjs/statemanager
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/verkle | AI (dependencies): Sibling package in the ethereumjs monorepo; same publisher/org, not an external unvetted dependency. | ai | |
| dependencies | unvetted-dep:@ethereumjs/mpt | AI (dependencies): First-party sibling dependency from the same ethereumjs-monorepo; published at matching version by the same maintainer team. | ai | |
| dependencies | unvetted-dep:@ethereumjs/rlp | AI (dependencies): First-party sibling dependency from the same ethereumjs-monorepo; published at matching version by the same maintainer team. | ai | |
| dependencies | unvetted-dep:@ethereumjs/util | AI (dependencies): First-party sibling dependency from the same ethereumjs-monorepo; published at matching version by the same maintainer team. | ai | |
| dependencies | unvetted-dep:@ethereumjs/common | AI (dependencies): First-party sibling dependency from the same ethereumjs-monorepo; published at matching version by the same maintainer team. | ai | |
| dependencies | unvetted-dep:@ethereumjs/binarytree | AI (dependencies): First-party sibling dependency from the same ethereumjs-monorepo; published at matching version by the same maintainer team. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.1.2 | 9 / 4 | |
| 10.1.1 | 9 / 4 | |
| 10.1.0 | 10 / 4 | |
| 10.0.0 | 11 / 3 |
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.