@ledgerhq/wallet-api-client
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Ledger's own CI publisher account, established track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org consolidating to CI-based publishing, not a takeover. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Likely used in compiled lib output; official Ledger package, stable dep. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in this package is standard hardware wallet transport protocol handling (converting device response hex strings to Buffers). Not a malicious payload pattern. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.15.2 | 3 / 10 | |
| 1.15.1 | 3 / 10 | |
| 1.15.0 | 3 / 10 | |
| 1.14.5 | 3 / 10 | |
| 1.14.4 | 3 / 10 | |
| 1.14.3 | 3 / 10 | |
| 1.14.2 | 3 / 10 | |
| 1.14.1 | 3 / 10 | |
| 1.14.0 | 3 / 10 | |
| 1.13.1 | 3 / 10 | |
| 1.13.0 | 3 / 10 | |
| 1.12.6 | 3 / 10 | |
| 1.12.5 | 3 / 10 | |
| 1.12.4 | 3 / 10 | |
| 1.12.3 | 3 / 10 | |
| 1.12.2 | 3 / 10 | |
| 1.12.1 | 3 / 10 | |
| 1.12.0 | 3 / 10 | |
| 1.11.1 | 3 / 10 | |
| 1.11.0 | 3 / 10 | |
| 1.10.0 | 3 / 10 | |
| 1.9.1 | 3 / 10 | |
| 1.9.0 | 3 / 10 | |
| 1.8.0 | 3 / 10 | |
| 1.7.5 | 3 / 10 | |
| 1.7.4 | 3 / 10 | |
| 1.7.3 | 3 / 10 | |
| 1.7.2 | 3 / 10 | |
| 1.7.1 | 3 / 10 | |
| 1.7.0 | 3 / 10 | |
| 1.6.2 | 3 / 10 | |
| 1.6.1 | 3 / 10 | |
| 1.6.0 | 3 / 10 | |
| 1.5.11 | 3 / 10 | |
| 1.5.10 | 3 / 10 | |
| 1.5.9 | 3 / 10 | |
| 1.5.8 | 3 / 10 | |
| 1.5.7 | 3 / 10 | |
| 1.5.6 | 3 / 10 | |
| 1.5.5 | 3 / 10 | |
| 1.5.4 | 3 / 10 | |
| 1.5.3 | 3 / 10 | |
| 1.5.2 | 3 / 10 | |
| 1.5.1 | 3 / 10 | |
| 1.5.0 | 3 / 10 | |
| 1.4.0 | 3 / 10 | |
| 1.3.0 | 3 / 10 | |
| 1.2.1 | 3 / 10 | |
| 1.2.0 | 3 / 10 | |
| 1.1.0 | 3 / 10 | |
| 1.0.3 | 3 / 10 | |
| 1.0.2 | 3 / 10 | |
| 1.0.1 | 3 / 10 | |
| 1.0.0 | 3 / 10 |
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-04-04. It has since remained available on npm for 838 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-04-02. It has since remained available on npm for 840 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-02-20. It has since remained available on npm for 881 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.