@metamask/images-example-snap
MetaMask example Snap demonstrating how to render images in Snaps UI
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uqr | AI (phantom-deps): Bundled Snap; deps consumed at build time, not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Same-org SDK used in Snap bundle build; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 2 / 16 | |
| 1.1.1 | 2 / 28 | |
| 1.1.0 | 2 / 28 | |
| 1.0.0 | 3 / 28 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.