@metamask/preinstalled-example-snap
MetaMask example snap demonstrating preinstalled Snaps
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publish with SLSA attestation; legitimate for MetaMask org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known MetaMask org members; legitimate transfer. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Snap bundle pattern; SDK is consumed at build time and bundled, not imported as a Node module at runtime. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 0 / 18 | |
| 0.7.2 | 1 / 20 | |
| 0.7.1 | 1 / 20 | |
| 0.7.0 | 1 / 20 | |
| 0.6.0 | 1 / 20 | |
| 0.5.0 | 1 / 20 | |
| 0.4.0 | 1 / 20 | |
| 0.3.0 | 1 / 33 | |
| 0.2.0 | 1 / 33 | |
| 0.1.0 | 1 / 32 |
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.