@ledgerhq/hw-app-btc
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:tests/splitTransaction.test.ts | AI (source-diff): Long hex strings are Bitcoin/Zcash transaction test fixtures, not malicious payloads. | ai | |
| source-diff | encoded-string-file:tests/createTransaction.test.ts | AI (source-diff): Long hex strings are Bitcoin/Zcash transaction test fixtures, not malicious payloads. | ai | |
| source-diff | encoded-string-file:lib/serializeTransaction.js | AI (source-diff): Long hex string is a Bitcoin transaction example in JSDoc documentation for serializeTransactionOutputs. Legitimate for this Bitcoin wallet library. | ai | |
| source-diff | encoded-string-file:lib/Btc.js | AI (source-diff): Long hex strings in Btc.js are Bitcoin transaction hex examples in JSDoc documentation, not obfuscated payloads. Expected for a Bitcoin hardware wallet library. | ai | |
| source-diff | encoded-string-file:lib-es/Btc.js | AI (source-diff): Long hex strings in Btc.js are Bitcoin transaction hex examples in JSDoc documentation, not obfuscated payloads. Expected for a Bitcoin hardware wallet library. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Bitcoin wallet library legitimately decodes hex-encoded transaction data and scripts. These are standard operations in Bitcoin protocol handling, not obfuscated payloads. | ai | |
| provenance | no-provenance | AI (provenance): Established LedgerHQ package published via CI automation from a known monorepo. Lack of Sigstore provenance is acceptable given the package's long history and ecosystem standing. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of cryptographic signatures is standard in a Bitcoin signing library. The sampled code shows legitimate signature parsing, not malicious payload handling. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 11.1.0 | 11 / 12 | |
| 11.0.1 | 11 / 12 | |
| 11.0.0 | 11 / 12 | |
| 10.22.1 | 11 / 12 | |
| 10.22.0 | 11 / 12 | |
| 10.21.1 | 11 / 12 | |
| 10.21.0 | 11 / 12 | |
| 10.20.1 | 11 / 12 | |
| 10.20.0 | 11 / 12 | |
| 10.19.0 | 11 / 12 | |
| 10.18.0 | 11 / 12 | |
| 10.17.0 | 11 / 12 | |
| 10.16.0 | 11 / 12 | |
| 10.15.0 | 11 / 11 | |
| 10.14.0 | 11 / 11 | |
| 10.13.1 | 11 / 11 | |
| 10.13.0 | 11 / 11 | |
| 10.12.0 | 11 / 11 | |
| 10.11.2 | 11 / 11 | |
| 10.11.1 | 11 / 11 | |
| 10.11.0 | 12 / 11 | |
| 10.10.2 | 12 / 11 | |
| 10.10.1 | 12 / 11 | |
| 10.10.0 | 12 / 11 | |
| 10.9.3 | 12 / 11 | |
| 10.9.2 | 12 / 12 | |
| 10.9.1 | 12 / 12 |
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.21.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.
v10.20.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.
v10.18.0
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.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.
v10.14.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.
v10.11.2
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.2
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.1
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
3 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.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.