@metamask/keyring-api
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): Legitimate migration from metamaskbot to GitHub Actions CI/CD; confirmed by SLSA provenance. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard MetaMask monorepo license pattern; stable across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active MetaMask monorepo package at v21.x; dormancy signal is a false positive given the version history and trusted publisher. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): @types/uuid is a type-only package; not directly imported at runtime by convention. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask org packages consistently lack Sigstore provenance; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 23.3.0 | 4 / 16 | |
| 23.2.0 | 4 / 16 | |
| 23.1.0 | 4 / 16 | |
| 23.0.1 | 4 / 16 | |
| 23.0.0 | 4 / 16 | |
| 22.0.0 | 4 / 17 | |
| 21.6.0 | 9 / 17 | |
| 21.5.0 | 9 / 17 | |
| 21.4.0 | 9 / 17 | |
| 21.3.0 | 4 / 17 | |
| 21.2.0 | 4 / 17 |
v23.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-10. 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.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.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.
v21.2.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.