@tronweb3/tronwallet-adapter-react-ui
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): Publisher change is 480d old, stable, and publisher has 71 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same historical transfer, no behavioral change in this version. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Change predates this version by 480d without takedown; not fresh. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No-op diff vs prior approved version; dormancy not paired with malicious change. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.13 | 2 / 15 | |
| 1.1.12 | 2 / 14 | |
| 1.1.11 | 2 / 14 | |
| 1.1.10 | 2 / 14 | |
| 1.1.9 | 2 / 14 |
v1.1.11
2 findingsThis version was published by a different npm account (tronwallet-adapter) than the most recent previously approved version (troncore) on 2025-03-25. It has since remained available on npm for 480 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.
v1.1.10
1 findingPackage 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.