ethereumjs-common
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Old, long-stable publisher transfer within trusted org, not a fresh takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Historical dormancy from 2020 release cadence, not recent anomalous activity. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 0 / 16 | |
| 1.5.1 | 0 / 16 | |
| 1.5.0 | 0 / 17 | |
| 1.4.0 | 0 / 17 | |
| 1.3.2 | 0 / 17 | |
| 1.3.1 | 0 / 17 | |
| 1.3.0 | 0 / 17 | |
| 1.2.1 | 0 / 17 | |
| 1.2.0 | 0 / 17 | |
| 1.1.0 | 0 / 16 | |
| 1.0.0 | 0 / 16 |
v1.5.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: evertonfraga.
This version was published by a different npm account (evertonfraga) than the most recent previously approved version (holgerd77) on 2020-05-06. It has since remained available on npm for 2267 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.