@socketsecurity/cli@1.1.154
CLI for Socket.dev
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows no npm lifecycle execution and no concrete malicious chain. Scanner hits map to expected CLI functionality, vendored terminal code, and a structured Maven extension archive.
Decision evidence
public snapshot- dist/cli.js has an explicit `socket install completion` command that writes its completion file and may append to ~/.bashrc.
- dist/cli.js can download GitHub manifest files only within an invoked repository-scan workflow.
- bin/cli.js launches the packaged CLI as a child process.
- package.json has no preinstall, install, postinstall, prepare, or uninstall lifecycle hook.
- bin/cli.js only runs when a CLI bin is invoked and forwards user arguments to dist/cli.js.
- Completion mutation is documented and gated behind the explicit `socket install completion` command.
- The flagged eval is in vendored terminal library external/blessed/lib/tput.js, not an install-time payload.
- The JAR is a named Maven extension archive with inspectable Coana/Maven classes, not a hidden executable payload.
- No source evidence of credential harvesting, stealth persistence, or foreign AI-agent control-surface mutation.
Source & flagged code
13 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.154.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.154 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.