@ledgerhq/hw-app-trx — Greenflagged

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

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

Keywords

LedgerLedgerWalletTronTrxNanoSBlueHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:lib-es/Trx.d.ts	AI (source-diff): Long hex strings in this file are JSDoc @example snippets showing sample Tron transaction hex data — expected documentation for a Tron hardware wallet library.	ai	2026/04/27
source-diff	encoded-string-file:lib/Trx.d.ts	AI (source-diff): Long hex strings in this file are JSDoc @example snippets showing sample Tron transaction hex data — expected documentation for a Tron hardware wallet library.	ai	2026/04/27
semgrep	semgrep:hex-decode	AI (semgrep): Buffer.from(rawTxHex, 'hex') is standard hex decoding for raw blockchain transaction bytes in a hardware wallet signing library. This pattern is expected and benign throughout this package.	ai	2026/04/26
dependencies	unvetted-dep:@ledgerhq/hw-transport	AI (dependencies): @ledgerhq/hw-transport is the canonical Ledger transport abstraction from the same LedgerHQ org; it is a core dependency for all hw-app-* packages and is stable/legitimate.	ai	2026/04/26

Versions (showing 20 of 20)

Version	Deps	Published
6.36.2	1 / 10	2026-06-05
6.36.1	1 / 10	2026-05-06
6.36.0	1 / 10	2026-04-22
6.35.0	1 / 10	2026-04-15
6.34.1	1 / 10	2026-03-26
6.34.0	1 / 10	2026-03-18
6.33.0	1 / 10	2026-03-12
6.32.0	1 / 10	2026-01-19
6.31.12	1 / 9	2026-01-13
6.31.11	1 / 9	2025-12-29
6.31.10	1 / 9	2025-12-17
6.31.9	1 / 9	2025-11-05
6.31.8	1 / 9	2025-10-01
6.31.7	1 / 9	2025-09-25
6.31.6	1 / 9	2025-09-05
6.31.5	1 / 9	2025-08-18
6.31.4	1 / 9	2025-07-23
6.31.3	1 / 9	2025-06-20
6.31.2	1 / 10	2025-06-06
6.31.1	1 / 10	2025-05-27

v6.36.2

1 finding

LOW No provenance attestation provenance

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

v6.36.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v6.34.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.34.0

3 findings

HIGH Long encoded string in modified file: lib-es/Trx.d.ts source-diff

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

HIGH Long encoded string in modified file: lib/Trx.d.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.

v6.33.0

3 findings

HIGH Long encoded string in modified file: lib-es/Trx.d.ts source-diff

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

HIGH Long encoded string in modified file: lib/Trx.d.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.

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

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

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

v6.31.9

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

1 finding

LOW No provenance attestation provenance

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

v6.31.7

1 finding

LOW No provenance attestation provenance

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

v6.31.6

1 finding

LOW No provenance attestation provenance

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

v6.31.5

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

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