@metamask/bitcoin-wallet-snap
A Bitcoin wallet Snap.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from metamaskbot to GitHub Actions CI with SLSA provenance; legitimate CI migration. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a recognized permissive license used by this package. | ai | |
| source-diff | encoded-string-file:dist/bundle.js | AI (source-diff): Webpack bundle with standard crypto utils; expected for a Snap package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): MetaMask org maintainer rotation; publisher metamaskbot is the canonical bot account. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 0 / 21 | |
| 1.12.0 | 0 / 21 | |
| 1.11.0 | 0 / 21 | |
| 1.10.1 | 0 / 21 |
v1.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.