@metamask/eth-snap-keyring
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 org migrated from metamaskbot to GitHub Actions CI; SLSA provenance confirms official repo. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard MetaMask pattern referencing a LICENSE file in the repo. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-sdk | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/snaps-utils | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-utils | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-snap-sdk | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/messenger | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-internal-api | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/keyring-internal-snap-client | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): @types/uuid is a type-only package; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-utils | AI (phantom-deps): Same-org transitive type usage; stable false positive. | ai | |
| dependencies | unvetted-dep:@metamask/snaps-controllers | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai | |
| dependencies | unvetted-dep:@metamask/snaps-sdk | AI (dependencies): First-party MetaMask package; stable false positive for this org-scoped package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 22.3.0 | 16 / 16 | |
| 22.2.0 | 16 / 16 | |
| 22.1.0 | 16 / 16 | |
| 22.0.1 | 16 / 16 | |
| 22.0.0 | 16 / 16 | |
| 21.0.1 | 16 / 16 | |
| 21.0.0 | 16 / 16 | |
| 20.0.0 | 16 / 15 | |
| 19.0.0 | 13 / 18 | |
| 18.0.2 | 12 / 18 | |
| 18.0.1 | 12 / 18 |
v22.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-11. 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.
v22.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.