@metamask/core-signer-example-snap
MetaMask example snap demonstrating how a snap can communicate with another snap to sign messages.
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:async-mutex | AI (phantom-deps): Snap bundle package; deps consumed at build time, not directly imported in analyzed source. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Snap bundle package; deps consumed at build time, not directly imported in analyzed source. | ai | |
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org dep used transitively in snap bundle; stable false positive. | ai | |
| phantom-deps | phantom-dep:@metamask/key-tree | AI (phantom-deps): Same-org dep used transitively in snap bundle; stable false positive. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Same-org dep used transitively in snap bundle; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 5 / 29 | |
| 2.1.2 | 5 / 29 | |
| 2.1.1 | 6 / 29 | |
| 2.1.0 | 6 / 29 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.