@ledgerhq/coin-bitcoin Apache-2.0 46 versions

@ledgerhq/coin-bitcoin

npm Repository Homepage

Ledger Bitcoin Coin integration

46

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

LedgerLedgerWalletbtcBitcoinHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:src/__tests__/unit/signRawOperation.test.ts	AI (source-diff): Long base64 string is a real PSBTv2 test fixture with explanatory comment; standard practice for Bitcoin wallet unit tests in this package.	ai	2026/04/27
semgrep	semgrep:hex-decode	AI (semgrep): Hex literals in this package are hardcoded protocol constants (e.g., address prefixes per Decred spec), not obfuscated payloads. False positive for a cryptocurrency library.	ai	2026/04/25
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get() used for a simple type guard check, not for API obfuscation. Idiomatic JavaScript pattern in this codebase.	ai	2026/04/25
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding appears only in test files for PSBT test fixtures. Not a malicious payload indicator.	ai	2026/04/25

Versions (showing 46 of 46)

Version	Deps	Published
0.42.0	30 / 26	2026-05-28
0.41.0	29 / 26	2026-05-21
0.40.0	29 / 26	2026-05-13
0.39.1	29 / 26	2026-05-06
0.39.0	29 / 26	2026-05-04
0.38.0	29 / 24	2026-04-22
0.37.0	29 / 24	2026-04-15
0.36.0	29 / 22	2026-04-01
0.35.0	29 / 22	2026-03-26
0.34.0	28 / 22	2026-03-18
0.33.0	28 / 22	2026-03-12
0.32.0	27 / 21	2026-03-03
0.31.1	27 / 21	2026-02-25
0.31.0	27 / 21	2026-02-17
0.30.2	27 / 21	2026-02-10
0.30.1	27 / 21	2026-01-30
0.30.0	27 / 21	2026-01-26
0.29.0	26 / 21	2026-01-19
0.28.0	26 / 20	2026-01-13
0.27.1	26 / 20	2025-12-31
0.27.0	26 / 20	2025-12-29
0.26.1	26 / 20	2025-12-17
0.26.0	26 / 20	2025-12-08
0.25.0	26 / 20	2025-11-20
0.24.0	26 / 20	2025-11-05
0.23.0	26 / 20	2025-10-16
0.22.2	26 / 20	2025-10-01
0.22.1	26 / 20	2025-09-25
0.22.0	28 / 20	2025-09-16
0.21.0	28 / 20	2025-09-05
0.20.2	28 / 20	2025-08-27
0.20.1	28 / 20	2025-08-18
0.20.0	28 / 20	2025-08-08
0.19.0	28 / 20	2025-07-31
0.18.0	28 / 20	2025-07-23
0.17.0	28 / 20	2025-07-17
0.16.3	28 / 20	2025-07-07
0.16.2	28 / 20	2025-06-27
0.16.1	28 / 20	2025-06-20
0.16.0	28 / 20	2025-06-17
0.15.8	28 / 21	2025-06-06
0.15.7	28 / 21	2025-05-27
0.15.6	28 / 21	2025-05-20
0.15.5	28 / 21	2025-05-13
0.15.4	28 / 20	2025-04-30
0.15.3	28 / 20	2025-04-25

v0.42.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.41.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.37.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.36.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.30.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.