@ledgerhq/ledger-key-ring-protocol Apache-2.0 35 versions

@ledgerhq/ledger-key-ring-protocol

npm Repository Homepage

Ledger Key Ring Protocol layer

35

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.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:src/__tests__/unit/sdk.test.ts	AI (source-diff): Long hex string is a mock TLS challenge TLV in a test fixture; not a malicious payload.	ai	2026/05/06
semgrep	semgrep:base64-decode	AI (semgrep): Base64 usage in qrcode/index.js is a standard round-trip validation check, not payload obfuscation. Stable false positive for this package.	ai	2026/04/26
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is in test files loading local scenario modules — standard test pattern, not a runtime security risk.	ai	2026/04/26
phantom-deps	phantom-dep:ws	AI (phantom-deps): ws is a declared runtime dependency in package.json; used via isomorphic-ws. False positive from config-file analysis.	ai	2026/04/26

Versions (showing 35 of 35)

Version	Deps	Published
0.14.0	13 / 11	2026-06-05
0.13.3	13 / 11	2026-05-28
0.13.2	13 / 11	2026-05-21
0.13.1	13 / 11	2026-05-06
0.13.0	13 / 11	2026-04-22
0.12.4	13 / 9	2026-04-15
0.12.3	13 / 9	2026-04-01
0.12.2	13 / 9	2026-03-26
0.12.1	13 / 9	2026-03-18
0.12.0	13 / 9	2026-03-12
0.11.5	13 / 8	2026-03-03
0.11.4	13 / 8	2026-02-25
0.11.3	13 / 8	2026-02-17
0.11.2	13 / 8	2026-02-10
0.11.1	13 / 8	2026-01-26
0.11.0	13 / 8	2026-01-19
0.10.0	13 / 7	2026-01-13
0.9.0	13 / 7	2025-12-29
0.8.1	13 / 7	2025-12-17
0.8.0	13 / 7	2025-12-08
0.7.1	13 / 7	2025-11-20
0.7.0	13 / 7	2025-11-05
0.6.8	13 / 7	2025-10-16
0.6.7	13 / 7	2025-10-01
0.6.6	13 / 7	2025-09-25
0.6.5	13 / 7	2025-09-16
0.6.4	13 / 7	2025-09-05
0.6.3	13 / 7	2025-08-27
0.6.2	13 / 7	2025-08-18
0.6.0	13 / 7	2025-07-23
0.5.11	13 / 7	2025-06-27
0.5.10	13 / 7	2025-06-20
0.5.9	13 / 7	2025-06-17
0.5.8	13 / 7	2025-06-06
0.5.7	13 / 7	2025-05-27

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.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.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.12.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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.5

2 findings

HIGH Long encoded string in modified file: src/__tests__/unit/sdk.test.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.11.4

2 findings

HIGH Long encoded string in modified file: src/__tests__/unit/sdk.test.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.11.3

1 finding

LOW No provenance attestation provenance

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

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

2 findings

HIGH Long encoded string in modified file: src/__tests__/unit/sdk.test.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.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.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

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

1 finding

LOW No provenance attestation provenance

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

v0.5.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.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

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