@ledgerhq/wallet-api-exchange-module
Wallet-API Exchange Module for Ledger Live
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ledgerhq/wallet-api-core | AI (dependencies): First-party Ledger HQ sibling package from the same LedgerHQ/ledger-live monorepo; unvetted status reflects pipeline ordering, not actual risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/wallet-api-client | AI (dependencies): First-party Ledger HQ sibling package from the same LedgerHQ/ledger-live monorepo; unvetted status reflects pipeline ordering, not actual risk. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI bot without Sigstore provenance; consistent across their monorepo packages. Not a risk signal for this publisher. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.30.0 | 3 / 3 | |
| 0.29.0 | 3 / 3 | |
| 0.28.0 | 3 / 3 | |
| 0.27.0 | 3 / 3 | |
| 0.26.0 | 3 / 1 | |
| 0.25.0 | 3 / 1 | |
| 0.24.0 | 3 / 1 | |
| 0.23.0 | 3 / 1 | |
| 0.22.0 | 3 / 1 | |
| 0.21.0 | 3 / 1 | |
| 0.20.0 | 3 / 1 | |
| 0.19.1 | 3 / 1 | |
| 0.19.0 | 3 / 1 | |
| 0.18.0 | 3 / 1 | |
| 0.17.0 | 3 / 1 | |
| 0.16.0 | 3 / 1 | |
| 0.15.0 | 3 / 1 | |
| 0.14.0 | 3 / 1 | |
| 0.13.0 | 2 / 1 |
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.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.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.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.