@metamask/test-snap-bip44
MetaMask BIP-44 Test Snap
1
Versions
ISC
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
naugturritavedanfinlaykumavisrekmarksmetamaskbotgudahttbrad.deckersethkfman
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eth-rpc-errors | AI (phantom-deps): Snap test package; deps referenced in config/snap manifest rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org dep used transitively in snap context; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@noble/bls12-381 | AI (phantom-deps): Crypto lib used in snap bundle; not directly imported in TS source but bundled via mm-snap build. | ai | |
| phantom-deps | phantom-dep:@metamask/key-tree | AI (phantom-deps): Same-org dep; stable false positive for this snap package. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-ui | AI (phantom-deps): Same-org dep; stable false positive for this snap package. | ai | |
| phantom-deps | phantom-dep:@metamask/rpc-methods | AI (phantom-deps): Same-org dep; stable false positive for this snap package. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-types | AI (phantom-deps): Same-org dep; stable false positive for this snap package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Test snap package; minimal README and no keywords are expected for internal MetaMask tooling. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.5.0 | 7 / 21 |
v5.5.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.