← Home

@bankofai/sun-cli

CLI tool for SUN.IO / SUNSWAP on TRON — for humans and AI agents

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

virtual_parsonroger.gangummy789jwzc1206bobo123123hhhleonatmoon

Keywords

tronsunswapsun.iodeficliai-agent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Common for npm packages; no other risk signals present to elevate this. ai
phantom-deps phantom-dep:tronweb AI (phantom-deps): tronweb is a declared runtime dep; likely used via @bankofai/sun-kit rather than directly imported in CLI layer. ai
phantom-deps phantom-dep:@scure/bip32 AI (phantom-deps): Declared dep; used transitively via wallet/kit dependencies, not directly in CLI source. ai
phantom-deps phantom-dep:@scure/bip39 AI (phantom-deps): Declared dep; used transitively via wallet/kit dependencies, not directly in CLI source. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 10 / 12
1.0.2 10 / 12
1.0.1 10 / 12
1.0.0 10 / 12

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.