@tsuga/cli@1.68.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime flow constrains credential destinations to Tsuga API hosts or loopback. Login and authenticated requests use the resolved API URL, with credentials stored under that URL.
Decision evidence
public snapshot- package.json lists build and packaging scripts but no npm install lifecycle hook.
- dist/cli.js accepts credentials only for the Tsuga API hosts or loopback hosts; other destinations are rejected.
- The login flow saves the session for the resolved API URL, and API requests send the token to that same URL.
Source & flagged code
13 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.68.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.68.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.