@tangle-network/sandbox-cli
CLI for Tangle Sandbox operations
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a transitive/config-referenced dep in this CLI package; stable false positive. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI tool with bundled ESM output; indirect imports expected. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): CLI tool with bundled ESM output; indirect imports expected. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): CLI tool with bundled ESM output; indirect imports expected. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI tool with bundled ESM output; indirect imports expected. | ai | |
| phantom-deps | phantom-dep:@tangle-network/sandbox | AI (phantom-deps): Same-org dependency; indirect usage in bundled CLI is expected. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.8 | 7 / 7 | |
| 0.2.7 | 7 / 7 | |
| 0.2.6 | 7 / 7 | |
| 0.2.5 | 6 / 7 | |
| 0.2.4 | 6 / 7 | |
| 0.2.2 | 5 / 5 | |
| 0.2.1 | 5 / 5 | |
| 0.2.0 | 5 / 5 | |
| 0.1.0 | 5 / 5 |
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.