@metamask/bip44-example-snap
MetaMask example snap demonstrating the use of `snap_getBip44Entropy`
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
Keywords
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 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 4 / 17 | |
| 2.1.3 | 4 / 29 | |
| 2.1.2 | 4 / 29 | |
| 2.1.1 | 5 / 29 | |
| 2.1.0 | 5 / 29 |
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.