@metamask/bip44-example-snap
MetaMask example snap demonstrating the use of `snap_getBip44Entropy`
1
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
danfinlaykumavismcmirerekmarksmetamaskbotgudahttnicholasellulsethkfmannaugtur
Keywords
MetaMaskSnapsEthereum
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org dep; snap bundle build tools resolve imports indirectly, not via direct require. | ai | |
| phantom-deps | phantom-dep:@noble/bls12-381 | AI (phantom-deps): Referenced in config files for snap build; indirect usage pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/key-tree | AI (phantom-deps): Same-org dep used via snap bundle toolchain; phantom-dep false positive stable for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Same-org dep; bundled snap pattern means direct imports may not appear as standard requires. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 4 / 17 |
v2.2.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.