@metamask/account-api
MetaMask Account API
7
Versions
MIT
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
accountmetamaskmultichain
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legit transition to CI/CD-attested publishing for official MetaMask org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers are known MetaMask team members; benign handoff. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 3 / 17 | |
| 1.1.0 | 3 / 17 | |
| 1.0.4 | 3 / 17 | |
| 1.0.3 | 3 / 17 | |
| 1.0.2 | 3 / 17 | |
| 1.0.1 | 3 / 17 | |
| 1.0.0 | 3 / 17 |
v1.1.1
1 finding
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.
v1.1.0
2 findings
HIGH
Publisher changed: metamaskbot → GitHub Actions (on 2026-07-09)
provenance
This version was published by a different npm account than previous versions on 2026-07-09. 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.