registry / @tsuga/cli / 1.123.0
@tsuga/cli@1.123.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is a CLI whose process and network use support its resource-management features. Its disclosed usage reporting is gated by explicit consent or opt-in, and the inspected authentication flow sends Tsuga credentials to the configured API service.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
CLI execution; usage telemetry requires TSUGA_TELEMETRY=1 or interactive consent.
Impact
Expected CLI service operations and opted-in usage reporting; no unauthorized collection or action was identified.
Mechanism
CLI commands use Tsuga API authentication for service requests. If enabled, usage reporting posts run metadata and spans to the resolved Tsuga API URL.
AI rationale
The package is a CLI whose process and network use support its resource-management features. Its disclosed usage reporting is gated by explicit consent or opt-in, and the inspected authentication flow sends Tsuga credentials to the configured API service.
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI entry point and declares no install lifecycle hook.
- Runtime usage reporting is gated by TSUGA_TELEMETRY or saved consent; otherwise the CLI asks whether to send usage data and saves the choice.
- The telemetry payload contains CLI version, platform, Node version, run metadata and spans, and is sent to the resolved Tsuga API URL.
- The CLI accepts Tsuga API hosts and uses its bearer token for API requests, consistent with its resource-management purpose.
- Telemetry command identification records recognized command names and skips option arguments.
Evidence against
- The bundle contains network and child-process code, but the network reporting path is consent-gated.
- The scanner flagged a critical-looking string, but the inspected context contains ordinary role and alert examples, not a credential or secret.
- The CLI stores and uses Tsuga authentication tokens, but the inspected request flow sends them to the configured API service.
Behavioral surface
ChildProcessCrypto
Source & flagged code
18 flaggeddist/cli.jsView file
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_oauth
severity = critical
line = 273
Critical
273patternName = github_server_token
severity = critical
line = 273
Critical
Secret Pattern
GitHub server-to-server token in dist/cli.js
dist/cli.jsFindings
9 Critical9 High2 Medium4 Low
CriticalCritical Secretdist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighTrigger Reachable Command Output Exfiltration
Affected versions and remediation
This report applies to @tsuga/cli@1.123.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.123.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.