@ledgerhq/hw-app-polkadot No license 51 versions

@ledgerhq/hw-app-polkadot

npm Repository Homepage

51

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

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

Keywords

LedgerLedgerWalletdotPolkadotNanoSBlueHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Ledger org internal maintainer rotation, long-stable on npm.	ai	2026/07/21
maintainer-change	maintainer-removed	AI (maintainer-change): Old Ledger maintainers rotated out, not a takeover pattern.	ai	2026/07/21
provenance	publisher-changed-stale	AI (provenance): Change is 1454d old and stable; consistent with legit transfer.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): LedgerHQ monorepo package; long dormancy between Polkadot-specific releases is expected. Published by the same trusted CI account with no other risk signals.	ai	2026/04/27
semgrep	semgrep:hex-decode	AI (semgrep): Buffer.from() calls in a hardware wallet signing API are standard binary data handling, not payload obfuscation. This is a stable false positive for this package.	ai	2026/04/26
dependencies	unvetted-dep:@zondax/ledger-substrate	AI (dependencies): Zondax is the official maintainer of Ledger apps for Substrate/Polkadot chains; this dependency is expected and legitimate for this hardware wallet library.	ai	2026/04/26

Versions (showing 51 of 74)

View all versions

Version	Deps	Published
6.38.6	4 / 10	2026-07-16
6.38.5	4 / 10	2026-06-30
6.38.4	4 / 10	2026-06-11
6.38.3	4 / 10	2026-06-05
6.38.2	4 / 10	2026-05-06
6.38.1	4 / 10	2026-04-22
6.38.0	4 / 10	2026-04-15
6.37.1	4 / 10	2026-03-26
6.37.0	4 / 10	2026-03-18
6.36.0	4 / 10	2026-03-12
6.35.0	4 / 10	2026-01-19
6.34.12	4 / 9	2026-01-13
6.34.11	4 / 9	2025-12-29
6.34.10	4 / 9	2025-12-17
6.34.9	4 / 9	2025-11-05
6.34.8	4 / 9	2025-10-01
6.34.7	4 / 9	2025-09-25
6.34.6	4 / 9	2025-09-05
6.34.5	4 / 9	2025-08-18
6.34.4	4 / 9	2025-07-23
6.34.3	4 / 9	2025-06-20
6.34.2	4 / 10	2025-06-06
6.34.1	4 / 10	2025-05-27
6.34.0	4 / 10	2025-04-11
6.33.0	4 / 10	2025-04-01
6.32.0	4 / 9	2024-10-08
6.31.4	4 / 9	2024-09-27
6.31.3	4 / 9	2024-09-17
6.31.2	4 / 9	2024-07-24
6.31.1	4 / 9	2024-07-19
6.31.0	4 / 9	2024-06-28
6.30.1	4 / 9	2024-07-03
6.30.0	4 / 9	2024-06-24
6.29.0	3 / 9	2024-06-18
6.28.6	3 / 9	2024-04-18
6.28.5	3 / 9	2024-03-19
6.28.4	3 / 9	2024-02-19
6.28.3	3 / 9	2024-01-31
6.28.2	3 / 9	2024-01-23
6.28.1	3 / 9	2023-12-12
6.28.0	3 / 9	2023-11-24
6.27.20	3 / 9	2023-11-09
6.27.19	3 / 9	2023-08-16
6.27.18	3 / 9	2023-08-07
6.27.17	3 / 9	2023-07-18
6.27.16	3 / 9	2023-06-23
6.27.15	3 / 9	2023-05-26
6.27.14	3 / 9	2023-05-09
6.27.13	3 / 10	2023-04-03
6.27.12	3 / 1	2023-02-15
6.27.11	3 / 1	2023-02-06

v6.38.6

1 finding

LOW No provenance attestation provenance

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

v6.38.5

1 finding

LOW No provenance attestation provenance

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

v6.34.0

1 finding

LOW No provenance attestation provenance

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

v6.33.0

1 finding

LOW No provenance attestation provenance

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

v6.32.0

1 finding

LOW No provenance attestation provenance

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

v6.31.4

1 finding

LOW No provenance attestation provenance

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

v6.31.3

1 finding

LOW No provenance attestation provenance

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

v6.31.2

1 finding

LOW No provenance attestation provenance

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

v6.31.1

1 finding

LOW No provenance attestation provenance

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

v6.31.0

1 finding

LOW No provenance attestation provenance

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

v6.30.1

1 finding

LOW No provenance attestation provenance

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

v6.30.0

1 finding

LOW No provenance attestation provenance

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

v6.29.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.

v6.28.6

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-04-18, unremoved on npm for 824d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-04-18. It has since remained available on npm for 824 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.5

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-03-19, unremoved on npm for 854d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-03-19. It has since remained available on npm for 854 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.4

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-02-19, unremoved on npm for 882d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-02-19. It has since remained available on npm for 882 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.3

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-01-31, unremoved on npm for 902d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-01-31. It has since remained available on npm for 902 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.2

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-01-23, unremoved on npm for 910d) provenance

This version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (juan-cortes) on 2024-01-23. It has since remained available on npm for 910 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.1

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-12-12, unremoved on npm for 951d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-12-12. It has since remained available on npm for 951 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.28.0

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-11-24, unremoved on npm for 969d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-11-24. It has since remained available on npm for 969 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.20

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-11-09, unremoved on npm for 985d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-11-09. It has since remained available on npm for 985 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.19

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-08-16, unremoved on npm for 1070d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-08-16. It has since remained available on npm for 1070 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.18

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-08-07, unremoved on npm for 1079d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-08-07. It has since remained available on npm for 1079 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.17

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-07-18, unremoved on npm for 1098d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-07-18. It has since remained available on npm for 1098 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.16

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-06-23, unremoved on npm for 1124d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-06-23. It has since remained available on npm for 1124 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.15

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-05-26, unremoved on npm for 1152d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-05-26. It has since remained available on npm for 1152 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.14

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-05-09, unremoved on npm for 1169d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-05-09. It has since remained available on npm for 1169 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.13

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-04-03, unremoved on npm for 1205d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-04-03. It has since remained available on npm for 1205 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.12

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-02-15, unremoved on npm for 1252d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-02-15. It has since remained available on npm for 1252 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v6.27.11

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-02-06, unremoved on npm for 1261d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-02-06. It has since remained available on npm for 1261 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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