@ethereumjs/tx
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @ethereumjs/tx is a scoped package in the well-known ethereumjs namespace; levenshtein match against 'pg' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @ethereumjs/tx is a scoped package in the well-known ethereumjs namespace; levenshtein match against 'qs' is a false positive with no impersonation intent. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.1.2 | 5 / 9 | |
| 10.1.1 | 5 / 9 | |
| 10.1.0 | 4 / 9 | |
| 10.0.0 | 4 / 8 |
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.