@metamask/keyring-controller
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): MetaMask migrated to GitHub Actions CI/CD publishing with SLSA provenance; stable for this org. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 27.0.0 | 15 / 18 | |
| 26.0.0 | 15 / 18 | |
| 25.5.0 | 15 / 18 | |
| 25.4.0 | 15 / 18 | |
| 25.3.0 | 15 / 18 | |
| 25.2.0 | 15 / 17 | |
| 25.1.1 | 15 / 17 | |
| 25.1.0 | 15 / 18 | |
| 25.0.0 | 15 / 18 |
v27.0.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.
v26.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.