@metamask/ppom-validator
This module has code to integrate Blockaid PPOM with MetaMask
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): metamaskbot-managed org publishing; maintainer churn is routine, not compromise indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): elliptic and json-rpc-random-id are established, widely-used libs fitting the package's crypto/RPC purpose. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a standard crypto library expected in Ethereum/MetaMask tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-n | AI (phantom-deps): eslint-plugin-n is a dev/lint tool accidentally listed in dependencies; not a real runtime phantom dep concern for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.39.2 | 10 / 31 | |
| 0.39.1 | 10 / 31 | |
| 0.37.0 | 8 / 33 | |
| 0.33.0 | 10 / 31 | |
| 0.2.0 | 5 / 30 | |
| 0.1.2 | 3 / 28 | |
| 0.1.1 | 3 / 28 |
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.