@ledgerhq/hw-transport-node-hid-noevents No license 70 versions

@ledgerhq/hw-transport-node-hid-noevents

npm Repository Homepage

70

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

LedgerLedgerWallethidnode-hidNanoSBlueHardware 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): Long-stable LedgerHQ org publish; new maintainers are Ledger team accounts.	ai	2026/07/25
maintainer-change	maintainer-removed	AI (maintainer-change): Old, stable transition (2022), not a recent takeover.	ai	2026/07/25
provenance	publisher-changed-stale	AI (provenance): Publisher change is stale (1457d), consistent with legitimate org handoff not compromise.	ai	2026/07/25

Versions (showing 70 of 70)

Version	Deps	Published
6.36.0	5 / 10	2026-06-30
6.35.4	5 / 10	2026-06-11
6.35.3	5 / 10	2026-06-05
6.35.2	5 / 10	2026-05-06
6.35.1	5 / 10	2026-04-22
6.35.0	5 / 10	2026-04-15
6.34.0	5 / 10	2026-03-26
6.33.0	5 / 10	2026-03-18
6.32.0	5 / 10	2026-03-12
6.31.0	5 / 10	2026-01-19
6.30.17	5 / 9	2026-01-13
6.30.16	5 / 9	2025-12-29
6.30.15	5 / 9	2025-12-17
6.30.14	5 / 9	2025-11-05
6.30.13	5 / 9	2025-10-01
6.30.12	5 / 9	2025-09-25
6.30.11	5 / 9	2025-09-05
6.30.10	5 / 9	2025-08-18
6.30.9	5 / 9	2025-07-23
6.30.8	5 / 9	2025-06-20
6.30.7	5 / 9	2025-06-06
6.30.6	5 / 9	2025-05-27
6.30.5	5 / 9	2024-09-27
6.30.4	5 / 9	2024-09-17
6.30.3	5 / 9	2024-07-24
6.30.2	5 / 9	2024-07-19
6.30.1	5 / 9	2024-06-28
6.30.0	5 / 9	2024-06-18
6.29.6	5 / 9	2024-04-18
6.29.5	5 / 9	2024-03-19
6.29.4	5 / 9	2024-02-19
6.29.3	5 / 9	2024-01-31
6.29.2	5 / 9	2024-01-23
6.29.1	5 / 9	2023-12-12
6.29.0	5 / 9	2023-11-24
6.28.0	5 / 9	2023-11-09
6.27.19	5 / 9	2023-08-16
6.27.18	5 / 9	2023-08-07
6.27.17	5 / 9	2023-07-18
6.27.16	5 / 9	2023-06-23
6.27.15	5 / 9	2023-05-26
6.27.14	5 / 9	2023-05-09
6.27.13	5 / 10	2023-04-03
6.27.12	5 / 1	2023-02-15
6.27.11	5 / 1	2023-02-06
6.27.10	5 / 1	2023-01-13
6.27.9	5 / 1	2022-12-22
6.27.8	5 / 1	2022-11-30
6.27.7	5 / 1	2022-11-18
6.27.6	5 / 1	2022-09-30
6.27.5	5 / 1	2022-09-28
6.27.4	5 / 1	2022-09-14
6.27.3	5 / 1	2022-08-31
6.27.2	5 / 1	2022-07-28
6.27.1	5 / 1	2022-04-13
6.24.1	5 / 1	2022-02-04
6.20.0	5 / 1	2021-12-16
6.19.0	5 / 1	2021-12-13
6.11.2	5 / 1	2021-10-28
6.11.0	5 / 1	2021-10-21
6.10.0	5 / 1	2021-10-18
6.7.0	5 / 1	2021-09-16
6.6.0	5 / 1	2021-09-06
6.3.0	5 / 1	2021-08-01
6.2.1	5 / 1	2021-07-28
6.2.0	5 / 1	2021-07-19
6.1.0	5 / 1	2021-07-06
6.0.2	5 / 1	2021-06-21
6.0.1	5 / 1	2021-06-21
6.0.0	5 / 1	2021-06-21

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

1 finding

LOW No provenance attestation provenance

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

v6.30.4

1 finding

LOW No provenance attestation provenance

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

v6.30.3

1 finding

LOW No provenance attestation provenance

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

v6.30.2

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.29.6

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-04-18, unremoved on npm for 827d) 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 827 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.29.5

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-03-19, unremoved on npm for 857d) 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 857 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.29.4

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-02-19, unremoved on npm for 886d) 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 886 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.29.3

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-01-31, unremoved on npm for 905d) 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 905 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.29.2

2 findings

MEDIUM Publisher changed: juan-cortes → ldg-github-ci (on 2024-01-23, unremoved on npm for 913d) 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 913 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.29.1

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-12-12, unremoved on npm for 955d) 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 955 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.29.0

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-11-24, unremoved on npm for 973d) 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 973 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-09, unremoved on npm for 988d) 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 988 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 1073d) 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 1073 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 1082d) 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 1082 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 1102d) 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 1102 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 1127d) 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 1127 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 1155d) 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 1155 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 1172d) 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 1172 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 1208d) 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 1208 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 1255d) 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 1255 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 1264d) 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 1264 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.10

2 findings

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

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2023-01-13. It has since remained available on npm for 1288 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.9

2 findings

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

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-12-22. It has since remained available on npm for 1310 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.8

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-11-30, unremoved on npm for 1332d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-11-30. It has since remained available on npm for 1332 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.7

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-11-18, unremoved on npm for 1344d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-11-18. It has since remained available on npm for 1344 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.6

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-09-30, unremoved on npm for 1393d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-30. It has since remained available on npm for 1393 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.5

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-09-28, unremoved on npm for 1395d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-28. It has since remained available on npm for 1395 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.4

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-09-14, unremoved on npm for 1409d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-09-14. It has since remained available on npm for 1409 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.3

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2022-08-31, unremoved on npm for 1424d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-08-31. It has since remained available on npm for 1424 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.2

2 findings

MEDIUM Publisher changed: gre → sergii-shkolin (on 2022-07-28, unremoved on npm for 1457d) provenance

This version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-07-28. It has since remained available on npm for 1457 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.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gre → juan-cortes (on 2022-04-13, known maintainer) provenance

This version was published by a different npm account (juan-cortes) than the most recent previously approved version (gre) on 2022-04-13, but juan-cortes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v6.24.1

1 finding

LOW No provenance attestation provenance

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

v6.20.0

1 finding

LOW No provenance attestation provenance

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

v6.19.0

1 finding

LOW No provenance attestation provenance

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

v6.11.2

1 finding

LOW No provenance attestation provenance

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

v6.11.0

1 finding

LOW No provenance attestation provenance

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

v6.10.0

1 finding

LOW No provenance attestation provenance

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

v6.7.0

1 finding

LOW No provenance attestation provenance

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

v6.6.0

1 finding

LOW No provenance attestation provenance

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

v6.3.0

1 finding

LOW No provenance attestation provenance

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

v6.2.1

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.2

1 finding

LOW No provenance attestation provenance

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

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

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