@tronweb3/tronwallet-adapters
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 usage in bundled wallet adapter is standard encoding for address/signing operations, not payload obfuscation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard cryptographic/address handling in a blockchain wallet adapter. | ai | |
| source-diff | encoded-string-file:lib/umd/index.js | AI (source-diff): Encoded string is the documented ENS normalize compressed data blob with cited SHA-256; not malicious. | ai | |
| source-diff | encoded-string-file:lib/umd/index.min.js | AI (source-diff): Minified bundle containing same ENS/crypto utility code; no obfuscation or malicious payload. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.26 | 22 / 3 | |
| 1.2.25 | 21 / 3 | |
| 1.2.24 | 20 / 3 | |
| 1.2.17 | 14 / 5 | |
| 1.2.15 | 14 / 6 | |
| 1.2.14 | 14 / 6 | |
| 1.2.13 | 13 / 6 | |
| 1.2.12 | 13 / 6 | |
| 1.2.11 | 13 / 6 | |
| 1.2.10 | 12 / 6 | |
| 1.2.9 | 11 / 6 |
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
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.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.