@metamask/error-example-snap
MetaMask example snap demonstrating the use of error handling in snaps.
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 |
|---|---|---|---|---|
| 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 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 28 | |
| 2.1.2 | 1 / 28 | |
| 2.1.1 | 1 / 28 | |
| 2.1.0 | 1 / 28 | |
| 2.0.1 | 1 / 28 | |
| 2.0.0 | 1 / 28 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.