@metamask/eth-ledger-bridge-keyring
A MetaMask compatible keyring, for ledger hardware wallets
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): Moved to GitHub Actions CI/CD publishing with SLSA provenance; expected for MetaMask org. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/context-module | AI (phantom-deps): Declared dep used transitively by Ledger SDK; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask org packages consistently publish without Sigstore provenance; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 12.2.0 | 14 / 26 | |
| 12.1.0 | 10 / 26 | |
| 12.0.3 | 10 / 26 | |
| 12.0.2 | 9 / 27 | |
| 12.0.1 | 9 / 27 | |
| 12.0.0 | 9 / 27 | |
| 11.4.0 | 10 / 27 | |
| 11.3.1 | 10 / 26 | |
| 11.3.0 | 9 / 26 | |
| 11.2.0 | 8 / 26 |
v12.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-12. 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.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.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.
v11.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.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.
v11.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.