@metamask/slip44
6
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
kumavisfrederikboldingmetamaskbotgudahttmrtenmcmirenaugtur
Keywords
BlockchainCryptocurrencyCryptography
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 manual (metamaskbot) to CI/CD (GitHub Actions) is an improvement, not a risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known MetaMask org members; stable for this scoped package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): danfinlay removal consistent with MetaMask org maintainer rotation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.5.0 | 0 / 23 | |
| 4.4.0 | 0 / 23 | |
| 4.3.0 | 0 / 23 | |
| 4.2.0 | 0 / 23 | |
| 4.1.0 | 0 / 23 | |
| 4.0.0 | 0 / 23 |
v4.5.0
2 findings
HIGH
Publisher changed: metamaskbot → GitHub Actions (on 2026-07-02)
provenance
This version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.