@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, so a manually published version cannot be tied back to a reviewed commit.
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 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.33.0 | 3 / 3 | |
| 0.32.0 | 3 / 3 | |
| 0.31.0 | 3 / 3 | |
| 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 | |
| 0.12.0 | 2 / 1 | |
| 0.11.0 | 2 / 1 | |
| 0.10.0 | 2 / 1 | |
| 0.9.0 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.1 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 2 / 5 |
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.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.