← Home

@ledgerhq/device-signer-kit-bitcoin

This module provides the implementation of the Ledger Bitcoin signer of the Device Management Kit. It enables interaction with the Bitcoin application on a Ledger device including:

5
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@types/crypto-js AI (dependencies): @types/crypto-js is a well-known TypeScript type definition package for crypto-js; no security risk for this LedgerHQ package. ai
provenance no-provenance AI (provenance): LedgerHQ is an established publisher with a clean track record; lack of provenance attestation is common and not a risk signal here. ai
phantom-deps phantom-dep:@types/crypto-js AI (phantom-deps): @types/crypto-js is a TypeScript type package; not being directly imported in source is expected behavior for type-only packages used at compile time. ai

Versions (showing 5 of 5)

Version Deps Published
1.3.1 6 / 10
1.3.0 6 / 10
1.2.0 6 / 10
1.0.2 6 / 10
1.0.1 6 / 10

v1.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.0.2

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.

v1.0.1

1 finding
INFO No provenance attestation provenance

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