@tronweb3/tronwallet-adapter-ledger
Wallet adapter for the Ledger wallet.
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib/umd/index.js | AI (source-diff): Documented ens-normalize compressed data blob bundled in UMD build, not payload obfuscation. | ai | |
| source-diff | encoded-string-file:lib/umd/index.min.js | AI (source-diff): Standard minified bundle output (base64 helper code), not obfuscation. | ai | |
| phantom-deps | phantom-dep:@testing-library/jest-dom | AI (phantom-deps): Test/framework dependency loaded by convention, not directly imported. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex buffer parsing is standard for blockchain address/tx handling in this TRON wallet adapter. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): eventemitter3 is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.1.14 | 9 / 4 | |
| 1.1.13 | 9 / 4 | |
| 1.1.12 | 7 / 3 | |
| 1.1.11 | 7 / 3 | |
| 1.1.9 | 7 / 3 | |
| 1.1.7 | 7 / 3 | |
| 1.1.6 | 7 / 3 | |
| 1.1.5 | 7 / 2 | |
| 1.1.4 | 7 / 2 | |
| 1.1.3 | 7 / 2 | |
| 1.1.2 | 7 / 2 | |
| 1.1.1 | 7 / 1 | |
| 1.0.0 | 8 / 1 |
v1.1.14
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.