@ledgerhq/coin-tester-bitcoin
Ledger BTC Coin Tester
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:bitcoin-core | AI (dependencies): bitcoin-core is a standard RPC client for Bitcoin Core nodes, appropriate for a Bitcoin coin tester package. | ai | |
| dependencies | unvetted-dep:bitcoinjs-lib | AI (dependencies): bitcoinjs-lib is the canonical Bitcoin JS library, expected dependency for any Bitcoin-related package. | ai | |
| dependencies | unvetted-dep:docker-compose | AI (dependencies): docker-compose is used to spin up Bitcoin test environments; appropriate for a coin tester package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-tester | AI (dependencies): Sibling LedgerHQ package from the same monorepo; expected dependency for this coin tester module. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is core to Bitcoin transaction/PSBT parsing. Buffer.from(hex, 'hex') is standard Bitcoin protocol handling, not payload obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI bot from the official ledger-live monorepo; lack of Sigstore attestation is acceptable given clear repo attribution. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): This testing tool legitimately passes process.env to child processes (Docker, Bitcoin Core). Standard subprocess env forwarding, not credential exfiltration. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.10.4 | 18 / 10 | |
| 1.10.3 | 18 / 10 | |
| 1.10.2 | 18 / 10 | |
| 1.10.1 | 18 / 10 | |
| 1.10.0 | 18 / 10 | |
| 1.9.0 | 18 / 11 | |
| 1.8.1 | 18 / 9 | |
| 1.8.0 | 18 / 9 | |
| 1.7.0 | 17 / 8 | |
| 1.6.0 | 17 / 8 | |
| 1.5.0 | 17 / 8 | |
| 1.4.4 | 17 / 8 | |
| 1.4.3 | 17 / 8 | |
| 1.4.2 | 17 / 8 | |
| 1.4.1 | 17 / 8 | |
| 1.4.0 | 17 / 8 | |
| 1.3.1 | 12 / 8 | |
| 1.3.0 | 12 / 8 | |
| 1.2.5 | 12 / 7 | |
| 1.2.4 | 12 / 7 | |
| 1.2.3 | 12 / 7 | |
| 1.2.2 | 12 / 7 | |
| 1.2.1 | 12 / 7 | |
| 1.2.0 | 12 / 7 | |
| 1.1.0 | 12 / 7 |
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
7 findingsSpreading entire process.env into an object — may capture all secrets 8 | cwd, 9 | log: Boolean(process.env.DEBUG), > 10 | env: { 11 | ...process.env, 12 | },
Spreading entire process.env into an object — may capture all secrets 15 | const { out } = await compose.logs("atlas", { 16 | cwd, > 17 | env: { 18 | ...process.env, 19 | },
Spreading entire process.env into an object — may capture all secrets 47 | cwd, 48 | log: Boolean(process.env.DEBUG), > 49 | env: { 50 | ...process.env, 51 | },
Spreading entire process.env into an object — may capture all secrets 54 | const { out } = await compose.logs("atlas", { 55 | cwd, > 56 | env: { 57 | ...process.env, 58 | },
Spreading entire process.env into an object — may capture all secrets 12 | cwd, 13 | log: Boolean(process.env.DEBUG), > 14 | env: { 15 | ...process.env, 16 | },
Spreading entire process.env into an object — may capture all secrets 20 | const { out } = await compose.logs("atlas", { 21 | cwd, > 22 | env: { 23 | ...process.env, 24 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.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.
v1.8.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.
v1.7.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.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.