@tronweb3/tronwallet-adapter-react-hooks
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-added | AI (maintainer-change): Org-wide transition to tronwallet-adapter account, verified track record across 70 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with same org-wide maintainer transition, not takeover. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.12 | 2 / 12 | |
| 1.1.11 | 2 / 8 | |
| 1.1.10 | 2 / 8 | |
| 1.1.9 | 2 / 8 | |
| 1.1.8 | 2 / 8 |
v1.1.10
2 findingsThis version was published by a different npm account than previous versions on 2025-03-25. 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.
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.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.