@dynamic-labs-sdk/tron
This package contains the TRON integration for the Dynamic SDK. It enables support for TRON external wallets.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established Tron ecosystem packages matching the package's stated purpose. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files consistent with adding Tron wallet adapter integration; no malicious indicators. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth matches addition of tronweb and wallet adapter dependencies/bindings. | ai | |
| dependencies | unvetted-dep:@tronweb3/tronwallet-adapters | AI (dependencies): Expected dependency for a Tron wallet SDK integration; stable and appropriate for this package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): CI-published monorepo package; provenance absence is consistent across all versions in this ecosystem. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 6 / 2 | |
| 1.5.0 | 6 / 2 | |
| 1.4.0 | 6 / 2 | |
| 1.3.0 | 6 / 2 | |
| 0.26.1 | 6 / 2 | |
| 0.23.0 | 6 / 2 | |
| 0.19.0 | 6 / 2 | |
| 0.18.1 | 6 / 2 | |
| 0.13.0 | 6 / 2 | |
| 0.8.0 | 6 / 2 | |
| 0.2.3 | 2 / 2 |
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.