tronweb
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in tronweb is used for standard keccak256-based contract address derivation (TRON/Ethereum CREATE pattern). Not a malicious payload — stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 9 / 54 | |
| 6.2.0 | 9 / 57 | |
| 6.1.1 | 9 / 57 | |
| 6.1.0 | 9 / 58 | |
| 6.0.4 | 9 / 58 | |
| 6.0.3 | 9 / 58 | |
| 6.0.2 | 9 / 54 | |
| 6.0.1 | 9 / 54 | |
| 6.0.0 | 9 / 54 | |
| 5.3.5 | 13 / 32 |
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.