@metamask/phishing-warning
A page to warn users about a suspected phishing site.
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
danfinlaykumavismetamaskbot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): README links are phishing site URLs — core content of this anti-phishing warning page, not spam. | ai | |
| phantom-deps | phantom-dep:ses | AI (phantom-deps): Bundled browser build; deps consumed at build time, not via direct import. | ai | |
| phantom-deps | phantom-dep:punycode | AI (phantom-deps): Bundled browser build; deps consumed at build time, not via direct import. | ai | |
| phantom-deps | phantom-dep:readable-stream | AI (phantom-deps): Bundled browser build; deps consumed at build time, not via direct import. | ai | |
| phantom-deps | phantom-dep:eth-phishing-detect | AI (phantom-deps): Bundled browser build; deps consumed at build time, not via direct import. | ai | |
| phantom-deps | phantom-dep:@metamask/design-tokens | AI (phantom-deps): Same-org dep used in bundled build; stable false positive. | ai | |
| phantom-deps | phantom-dep:@metamask/object-multiplex | AI (phantom-deps): Same-org dep used in bundled build; stable false positive. | ai | |
| phantom-deps | phantom-dep:@metamask/post-message-stream | AI (phantom-deps): Same-org dep used in bundled build; stable false positive. | ai |
v5.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.