@metamask/eth-sig-util
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 | no-provenance | AI (provenance): MetaMask publishes via their automation bot (metamaskbot); lack of Sigstore provenance is consistent across their packages and does not indicate supply chain risk for this established org. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 8.2.0 | 7 / 25 | |
| 8.1.2 | 6 / 25 | |
| 8.1.1 | 6 / 25 | |
| 8.1.0 | 6 / 25 | |
| 8.0.0 | 6 / 25 |
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.