@metamask/error-example-snap
MetaMask example snap demonstrating the use of error handling in snaps.
1
Versions
(MIT-0 OR Apache-2.0)
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
mcmirenicholasellullgbotnaugturritavedanfinlaykumavisrekmarksmetamaskbotgudahttsethkfman
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Snap bundle; SDK is consumed at build time by mm-snap, not directly imported in source — stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally minimal example snap; sparse README and no keywords are expected for this package type. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 28 |
v2.1.3
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.