← Home

@metamask/send-flow-example-snap

npm Repository Homepage

MetaMask example Snap demonstrating a send flow with UI components

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

danfinlaykumavismetamaskbotgudahtt

Keywords

MetaMaskSnapsEthereum

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@metamask/utils AI (phantom-deps): Transitive dependency via @metamask/snaps-sdk; stable for this package. ai
phantom-deps phantom-dep:@metamask/snaps-sdk AI (phantom-deps): Direct dependency used by build tooling and runtime; false positive. ai
phantom-deps phantom-dep:@metamask/rpc-errors AI (phantom-deps): Transitive dependency via @metamask/snaps-sdk; stable for this package. ai

Versions (showing 6 of 6)

Version Deps Published
1.2.1 0 / 19
1.2.0 3 / 16
1.1.2 3 / 16
1.1.1 3 / 16
1.1.0 2 / 16
1.0.0 2 / 29

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.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.