← Home

@ledgerhq/live-wallet

npm Repository Homepage

Ledger Live wallet

36
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

Ledger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ledgerhq/compressjs AI (dependencies): Pinned to a specific commit in the LedgerHQ org; stable pattern across versions of this package. ai
npm-metadata url-dep:@ledgerhq/compressjs AI (npm-metadata): Commit-pinned GitHub dep within LedgerHQ org; not an arbitrary swappable URL. ai
dependencies unvetted-dep:@ledgerhq/ledger-key-ring-protocol AI (dependencies): @ledgerhq/ledger-key-ring-protocol is a first-party LedgerHQ package; its use here is expected and consistent with the Ledger Live ecosystem. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in a Jest mock file (src/walletsync/__mocks__/index.ts), not production code. No runtime risk to consumers. ai
bogus-package bogus-package AI (bogus-package): Package is a component of the LedgerHQ monorepo; sparse README and small sub-entry-point are expected for internal library packages. ai

Versions (showing 36 of 36)

Version Deps Published
0.27.1 16 / 12
0.27.0 16 / 12
0.26.0 16 / 12
0.25.3 16 / 12
0.25.2 16 / 12
0.25.1 16 / 12
0.25.0 16 / 12
0.24.0 16 / 12
0.23.0 16 / 11
0.22.0 16 / 11
0.21.4 16 / 11
0.21.3 16 / 11
0.21.2 16 / 11
0.21.1 16 / 11
0.21.0 16 / 11
0.20.1 16 / 11
0.20.0 16 / 11
0.19.0 16 / 11
0.18.0 16 / 10
0.17.1 16 / 10
0.17.0 16 / 10
0.16.2 16 / 10
0.16.1 16 / 10
0.16.0 16 / 10
0.15.0 16 / 10
0.14.3 16 / 10
0.14.2 16 / 10
0.14.1 16 / 10
0.14.0 16 / 10
0.12.2 18 / 10
0.12.1 18 / 10
0.11.6 18 / 10
0.11.0 18 / 10
0.10.10 18 / 10
0.10.7 18 / 10
0.10.6 18 / 10

v0.27.1

1 finding
LOW No provenance attestation provenance

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

v0.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.3

1 finding
LOW No provenance attestation provenance

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

v0.25.2

1 finding
LOW No provenance attestation provenance

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

v0.25.1

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.25.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.24.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.23.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.14.3

1 finding
LOW No provenance attestation provenance

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

v0.14.2

1 finding
LOW No provenance attestation provenance

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

v0.14.1

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.14.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.12.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.

v0.12.1

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.11.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.11.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.10.10

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