@ledgerhq/device-core No license 44 versions

@ledgerhq/device-core

npm Repository Homepage

44

Versions

—

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

Ledger

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 encoding/decoding is used for constructing binary protocol buffers for Ledger hardware wallet communication — standard and expected in this hardware wallet SDK.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/logs	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/errors	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/devices	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/types-live	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/hw-transport	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25
dependencies	unvetted-dep:@ledgerhq/live-network	AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ organization; expected internal dependency.	ai	2026/04/25

Versions (showing 44 of 44)

Version	Deps	Published
0.11.2	8 / 12	2026-06-05
0.11.1	8 / 12	2026-05-28
0.11.0	8 / 12	2026-05-21
0.10.2	8 / 12	2026-05-06
0.10.1	8 / 12	2026-05-04
0.10.0	8 / 12	2026-04-22
0.9.4	8 / 10	2026-04-15
0.9.3	8 / 10	2026-04-01
0.9.2	8 / 10	2026-03-26
0.9.1	8 / 10	2026-03-18
0.9.0	8 / 10	2026-03-12
0.8.6	8 / 10	2026-03-03
0.8.5	8 / 10	2026-02-25
0.8.4	8 / 10	2026-02-17
0.8.3	8 / 10	2026-02-10
0.8.2	8 / 10	2026-01-30
0.8.1	8 / 10	2026-01-26
0.8.0	8 / 10	2026-01-19
0.7.0	8 / 8	2026-01-13
0.6.12	8 / 8	2025-12-31
0.6.11	8 / 8	2025-12-29
0.6.10	8 / 8	2025-12-17
0.6.9	8 / 8	2025-12-08
0.6.8	8 / 8	2025-11-20
0.6.7	8 / 8	2025-11-05
0.6.6	8 / 8	2025-10-16
0.6.5	8 / 8	2025-10-01
0.6.4	8 / 8	2025-09-25
0.6.3	8 / 8	2025-09-16
0.6.2	8 / 8	2025-09-05
0.6.1	8 / 8	2025-08-27
0.6.0	8 / 8	2025-08-18
0.5.5	8 / 8	2025-08-08
0.5.4	8 / 8	2025-07-31
0.5.3	8 / 8	2025-07-23
0.5.2	8 / 8	2025-07-17
0.5.1	8 / 8	2025-07-07
0.5.0	8 / 8	2025-06-27
0.4.28	8 / 8	2025-06-20
0.4.27	8 / 8	2025-06-17
0.4.26	8 / 8	2025-06-06
0.4.25	8 / 8	2025-05-27
0.4.24	8 / 8	2025-05-13
0.4.23	8 / 8	2025-04-30

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.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.9.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.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.6.6

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.28

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.4.27

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.4.26

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.4.25

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.4.24

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.4.23

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.