@metamask/client-status-example-snap
MetaMask example snap demonstrating the use of `snap_getClientStatus`.
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): snaps-sdk is bundled into dist/bundle.js by mm-snap build; not directly imported in source but legitimately declared as a runtime dep. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 1 / 29 | |
| 1.0.2 | 1 / 29 | |
| 1.0.1 | 2 / 29 | |
| 1.0.0 | 2 / 29 |
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.