@metamask/client-mcp-core
HTTP daemon and CLI for agent-driven browser extension testing with Playwright
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@metamask/device-mcp | AI (dependencies): First-party MetaMask package, not third-party unvetted code. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known MetaMask org maintainers, consistent with CI provenance improvement. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 4 / 34 | |
| 0.5.0 | 3 / 34 | |
| 0.4.0 | 3 / 34 | |
| 0.3.0 | 3 / 34 | |
| 0.2.0 | 3 / 34 | |
| 0.1.1 | 2 / 33 | |
| 0.1.0 | 2 / 33 |
v0.6.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metamaskbot) on 2026-07-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.