← Home

@metamask/consumer-signer-example-snap

npm Repository

MetaMask example snap demonstrating how a snap can communicate with another snap to sign messages.

6
Versions
(MIT-0 OR Apache-2.0)
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mcmirenicholasellullgbotnaugturritavedanfinlaykumavisrekmarksmetamaskbotgudahttsethkfman

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@metamask/key-tree AI (phantom-deps): Same-org dep in a bundled snap; phantom-dep heuristic is a false positive for this package. ai
phantom-deps phantom-dep:@metamask/snaps-sdk AI (phantom-deps): Same-org dep in a bundled snap; phantom-dep heuristic is a false positive for this package. ai
phantom-deps phantom-dep:@metamask/utils AI (phantom-deps): Same-org dep in a bundled snap; phantom-dep heuristic is a false positive for this package. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): Used transitively in bundled snap output; phantom-dep heuristic is a false positive here. ai
bogus-package bogus-package AI (bogus-package): Minimal README is expected for an official example snap in a monorepo; not spam. ai

Versions (showing 6 of 6)

Version Deps Published
2.1.3 4 / 28
2.1.2 4 / 28
2.1.1 5 / 28
2.1.0 5 / 28
2.0.1 5 / 28
2.0.0 5 / 28

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.