@ledgerhq/wallet-api-server
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of cryptographic signatures and binary payloads is standard and expected in a blockchain wallet API server. Not a malicious payload indicator for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped @ledgerhq monorepo package with 76 versions and 1292 days of history. Missing metadata fields are a quality issue, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): bignumber.js is a legitimate runtime dependency for numeric precision in crypto/wallet operations; phantom-dep heuristic may miss usage in compiled TypeScript output. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.3.4 | 3 / 10 | |
| 3.3.3 | 3 / 10 | |
| 3.3.2 | 3 / 10 | |
| 3.3.1 | 3 / 10 | |
| 3.3.0 | 3 / 10 | |
| 3.2.0 | 3 / 10 | |
| 3.1.0 | 3 / 10 | |
| 3.0.0 | 3 / 10 | |
| 2.0.1 | 3 / 12 | |
| 2.0.0 | 3 / 12 |
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.