@ledgerhq/hw-transport-mocker No license 68 versions

@ledgerhq/hw-transport-mocker

npm Repository Homepage

68

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

LedgerLedgerWalletNanoSBlueHardware 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): Known historical Ledger team maintainer rotation, stable for years.	ai	2026/07/21
maintainer-change	maintainer-removed	AI (maintainer-change): Same rotation event, not a takeover.	ai	2026/07/21
provenance	publisher-changed-stale	AI (provenance): Old, stable publisher change on official Ledger package, not indicative of compromise.	ai	2026/07/21
semgrep	semgrep:hex-decode	AI (semgrep): This package is a hardware wallet transport mocker; hex decoding of APDU data is a core, expected operation. Not a malicious payload indicator.	ai	2026/04/26

Versions (showing 68 of 68)

Version	Deps	Published
6.34.6	3 / 9	2026-07-16
6.34.5	3 / 9	2026-06-30
6.34.4	3 / 9	2026-06-11
6.34.3	3 / 9	2026-06-05
6.34.2	3 / 9	2026-05-06
6.34.1	3 / 9	2026-04-22
6.34.0	3 / 9	2026-04-15
6.33.1	3 / 9	2026-03-26
6.33.0	3 / 9	2026-03-18
6.32.0	3 / 9	2026-03-12
6.31.0	3 / 9	2026-01-19
6.30.1	3 / 8	2026-01-13
6.30.0	3 / 8	2025-12-29
6.29.14	3 / 8	2025-12-17
6.29.13	3 / 8	2025-11-05
6.29.12	3 / 8	2025-10-01
6.29.11	3 / 8	2025-09-25
6.29.10	3 / 8	2025-09-05
6.29.9	3 / 8	2025-08-18
6.29.8	3 / 8	2025-07-23
6.29.7	3 / 8	2025-06-20
6.29.6	3 / 8	2025-06-06
6.29.5	3 / 8	2025-05-27
6.29.4	3 / 8	2024-09-27
6.29.3	3 / 8	2024-09-17
6.29.2	3 / 8	2024-07-24
6.29.1	3 / 8	2024-07-19
6.29.0	3 / 8	2024-06-18
6.28.6	3 / 8	2024-04-18
6.28.5	3 / 8	2024-03-19
6.28.4	3 / 8	2024-02-19
6.28.3	3 / 8	2024-01-31
6.28.2	3 / 8	2024-01-23
6.28.1	3 / 8	2023-12-12
6.28.0	3 / 8	2023-11-24
6.27.20	3 / 8	2023-11-09
6.27.19	2 / 8	2023-08-16
6.27.18	2 / 8	2023-08-07
6.27.17	2 / 8	2023-07-18
6.27.16	2 / 8	2023-06-23
6.27.15	2 / 8	2023-05-26
6.27.14	2 / 8	2023-05-09
6.27.13	2 / 9	2023-04-03
6.27.12	2 / 0	2023-02-15
6.27.11	2 / 0	2023-02-06
6.27.10	2 / 0	2023-01-13
6.27.9	2 / 0	2022-12-22
6.27.8	2 / 0	2022-11-30
6.27.7	2 / 0	2022-11-18
6.27.6	2 / 0	2022-09-30
6.27.5	2 / 0	2022-09-28
6.27.4	2 / 0	2022-09-14
6.27.3	2 / 0	2022-08-31
6.27.2	2 / 0	2022-07-28
6.27.1	2 / 0	2022-04-13
6.24.1	2 / 0	2022-02-04
6.20.0	2 / 0	2021-12-16
6.19.0	2 / 0	2021-12-13
6.11.2	2 / 0	2021-10-28
6.11.0	2 / 0	2021-10-21
6.10.0	2 / 0	2021-10-18
6.7.0	2 / 0	2021-09-16
6.3.0	2 / 0	2021-08-01
6.2.0	2 / 0	2021-07-19
6.1.0	2 / 0	2021-07-06
6.0.2	2 / 0	2021-06-21
6.0.1	2 / 0	2021-06-21
6.0.0	2 / 0	2021-06-21

v6.34.6

1 finding

LOW No provenance attestation provenance

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

v6.34.5

1 finding

LOW No provenance attestation provenance

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

v6.29.4

1 finding

LOW No provenance attestation provenance

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

v6.29.3

1 finding

LOW No provenance attestation provenance

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

v6.29.2

1 finding

LOW No provenance attestation provenance

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

v6.29.1

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.

v6.27.10

2 findings

MEDIUM Publisher changed: juan-cortes → sergii-shkolin (on 2023-01-13, unremoved on npm for 1284d) 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 1284 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 1307d) 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 1307 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 1329d) 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 1329 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 1340d) 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 1340 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 1390d) 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 1390 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 1392d) 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 1392 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 1406d) 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 1406 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 1420d) 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 1420 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: juan-cortes → sergii-shkolin (on 2022-07-28, unremoved on npm for 1454d) provenance

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