@ledgerhq/hw-app-trx
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Corresponding removal from same rotation, not a takeover pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Ledger team rotation across a large monorepo; publisher has long clean track record. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher stable on npm for 1454+ days, inconsistent with takeover. | ai | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 6.36.5 | 1 / 10 | |
| 6.36.4 | 1 / 10 | |
| 6.36.3 | 1 / 10 | |
| 6.36.2 | 1 / 10 | |
| 6.36.1 | 1 / 10 | |
| 6.36.0 | 1 / 10 | |
| 6.35.0 | 1 / 10 | |
| 6.34.1 | 1 / 10 | |
| 6.34.0 | 1 / 10 | |
| 6.33.0 | 1 / 10 | |
| 6.32.0 | 1 / 10 | |
| 6.31.12 | 1 / 9 | |
| 6.31.11 | 1 / 9 | |
| 6.31.10 | 1 / 9 | |
| 6.31.9 | 1 / 9 | |
| 6.31.8 | 1 / 9 | |
| 6.31.7 | 1 / 9 | |
| 6.31.6 | 1 / 9 | |
| 6.31.5 | 1 / 9 | |
| 6.31.4 | 1 / 9 | |
| 6.31.3 | 1 / 9 | |
| 6.31.2 | 1 / 10 | |
| 6.31.1 | 1 / 10 | |
| 6.31.0 | 1 / 10 | |
| 6.30.0 | 1 / 10 | |
| 6.29.4 | 1 / 9 | |
| 6.29.3 | 1 / 9 | |
| 6.29.2 | 1 / 9 | |
| 6.29.1 | 1 / 9 | |
| 6.29.0 | 1 / 9 | |
| 6.28.6 | 1 / 9 | |
| 6.28.5 | 1 / 9 | |
| 6.28.4 | 1 / 9 | |
| 6.28.3 | 1 / 9 | |
| 6.28.2 | 1 / 9 | |
| 6.28.1 | 1 / 9 | |
| 6.28.0 | 1 / 9 | |
| 6.27.20 | 1 / 9 | |
| 6.27.19 | 2 / 9 | |
| 6.27.18 | 2 / 9 | |
| 6.27.17 | 2 / 9 | |
| 6.27.16 | 2 / 9 | |
| 6.27.15 | 2 / 9 | |
| 6.27.14 | 2 / 9 | |
| 6.27.13 | 2 / 10 | |
| 6.27.12 | 2 / 1 | |
| 6.27.11 | 2 / 1 | |
| 6.27.10 | 2 / 1 | |
| 6.27.9 | 2 / 1 | |
| 6.27.8 | 2 / 1 | |
| 6.27.7 | 2 / 1 |
v6.36.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.28.6
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.5
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.20
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.19
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.18
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.17
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.16
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.15
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.14
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.13
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.12
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.11
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.10
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.9
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.8
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.7
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.