@tronweb3/tronwallet-abstract-adapter
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition occurred 291 days ago with strong subsequent track record (52 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same legitimate transition, consistent across many since-approved versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same vetted maintainer handoff, not a takeover pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tronweb is the official companion package in the same monorepo/ecosystem. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 2 / 2 | |
| 1.1.13 | 2 / 2 | |
| 1.1.12 | 2 / 2 | |
| 1.1.11 | 2 / 2 | |
| 1.1.10 | 2 / 1 | |
| 1.1.9 | 2 / 1 | |
| 1.1.7 | 1 / 1 | |
| 1.1.6 | 1 / 2 | |
| 1.1.5 | 1 / 2 | |
| 1.1.4 | 1 / 2 | |
| 1.1.3 | 1 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v1.1.9
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
2 findingsThis version was published by a different npm account (troncore) than the most recent previously approved version (tron-dev) on 2023-02-20. It has since remained available on npm for 1253 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.1
2 findingsThis version was published by a different npm account (troncore) than the most recent previously approved version (tron-dev) on 2023-02-06. It has since remained available on npm for 1267 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.0
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.