@metamask/bip32-example-snap
MetaMask example snap demonstrating the use of `snap_getBip32Entropy`
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:@noble/ed25519 | AI (phantom-deps): Used in snap bundle build; not directly imported in source but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@noble/secp256k1 | AI (phantom-deps): Used in snap bundle build; not directly imported in source but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org dep used transitively in snap bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/key-tree | AI (phantom-deps): Same-org dep used in snap bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Same-org dep used in snap bundle; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 5 / 16 | |
| 2.2.1 | 5 / 28 | |
| 2.2.0 | 5 / 28 | |
| 2.1.2 | 5 / 28 | |
| 2.1.1 | 6 / 28 | |
| 2.1.0 | 6 / 28 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
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. 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.