@dfns/lib-tron
Supply chain provenance
Status for the latest visible version.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is known prior maintainer per provenance record, not a takeover. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Likely used in bundled/compiled output; consistent with tron wallet libs. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is standard crypto dep for blockchain wallet signing. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps align with Tron blockchain functionality of the package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Focused SDK sub-package; tiny payload and missing metadata are expected for this library structure. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this SDK sub-package; not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Declared as runtime dep for browser polyfill; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-fetch | AI (phantom-deps): Declared as runtime dep for fetch polyfill; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 0.8.24 | 3 / 0 | |
| 0.8.23 | 3 / 0 | |
| 0.8.21 | 3 / 0 | |
| 0.8.20 | 3 / 0 | |
| 0.8.19 | 3 / 0 | |
| 0.8.18 | 3 / 0 | |
| 0.8.17 | 3 / 0 | |
| 0.8.13 | 3 / 0 | |
| 0.8.12 | 3 / 0 | |
| 0.8.11 | 3 / 0 | |
| 0.8.10 | 3 / 0 | |
| 0.8.9 | 3 / 0 | |
| 0.8.8 | 3 / 0 | |
| 0.8.7 | 3 / 0 | |
| 0.8.6 | 3 / 0 | |
| 0.8.5 | 3 / 0 | |
| 0.8.4 | 3 / 0 | |
| 0.8.3 | 3 / 0 | |
| 0.8.2 | 3 / 0 | |
| 0.8.1 | 3 / 0 | |
| 0.8.0 | 3 / 0 | |
| 0.7.18 | 1 / 0 | |
| 0.7.17 | 1 / 0 | |
| 0.7.16 | 1 / 0 | |
| 0.7.15 | 3 / 0 | |
| 0.7.14 | 1 / 0 | |
| 0.7.13 | 1 / 0 | |
| 0.7.12 | 1 / 0 | |
| 0.7.11 | 3 / 0 | |
| 0.7.10 | 3 / 0 | |
| 0.7.9 | 3 / 0 | |
| 0.7.8 | 3 / 0 | |
| 0.7.7 | 3 / 0 | |
| 0.7.6 | 3 / 0 | |
| 0.7.5 | 3 / 0 | |
| 0.7.4 | 3 / 0 | |
| 0.7.3 | 3 / 0 | |
| 0.7.2 | 3 / 0 | |
| 0.7.1 | 3 / 0 | |
| 0.7.0 | 1 / 0 | |
| 0.6.12 | 4 / 0 | |
| 0.6.11 | 4 / 0 | |
| 0.6.10 | 4 / 0 | |
| 0.6.9 | 4 / 0 | |
| 0.6.8 | 4 / 0 | |
| 0.6.7 | 4 / 0 | |
| 0.6.6 | 4 / 0 | |
| 0.6.5 | 4 / 0 | |
| 0.6.4 | 4 / 0 | |
| 0.6.3 | 4 / 0 | |
| 0.6.2 | 4 / 0 |
v0.8.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2026-02-12, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2026-02-05, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (thibault2ss) on 2026-01-30, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (thibault2ss) than the most recent previously approved version (drunkirishcoder) on 2026-01-19, but thibault2ss is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2026-01-07, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-11-19, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (luisalmeida-dfns) than the most recent previously approved version (adriendfns) on 2025-10-23, but luisalmeida-dfns is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adriendfns) than the most recent previously approved version (drunkirishcoder) on 2025-10-16, but adriendfns is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (thibault2ss) than the most recent previously approved version (drunkirishcoder) on 2025-06-13, but thibault2ss is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ncornwell) than the most recent previously approved version (drunkirishcoder) on 2025-04-04, but ncornwell is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (thibault2ss) on 2025-01-30, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.