@socketsecurity/cli@1.1.176
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time attack or covert payload was established. However, the active login path conditionally forwards a prompted credential to an unrestricted configured endpoint, which is a real dangerous capability.
Decision evidence
public snapshot- The login command accepts an arbitrary API server URL and prompts the user for a Socket API token.
- Configured environment or stored API base URLs only require URL syntax validation.
- The SDK is constructed with the token and the configured base URL, permitting conditional forwarding to that endpoint.
- The manifest exposes command-line binaries and has no preinstall, install, or postinstall lifecycle hook.
- The flagged terminal evaluator is part of bundled blessed terminal handling.
- The bundled npm fetcher removes authorization and cookies when redirects change hostname.
Source & flagged code
18 flaggedPackage source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152Findings
Affected versions and remediation
This report applies to @socketsecurity/cli@1.1.176.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.176 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.