@socketsecurity/cli@1.7.0
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 25d ago · by lpm-firewall-aiInspected source does not substantiate the scanner’s malicious verdict, and package.json has no install lifecycle hook. The required Maven extension JAR cannot be verified as source, so the package cannot be marked clean on this inspection.
Decision evidence
public snapshot- package.json lists CLI binaries and build scripts; no install lifecycle hook is present.
- bin/cli.js starts the packaged CLI, and dist/cli.js imports its vendor bundle and registry utilities.
- The flagged registry code shown reads GitHub Actions token variables and rejects when they are absent; this excerpt does not establish credential exfiltration.
- The required Maven extension JAR is binary, so its behavior could not be verified from source.
- The package identifies itself as a Socket.dev CLI and points to its SocketDev repository.
- The tput.js excerpt identifies a terminfo parser; it does not show dynamic evaluation.
Source & flagged code
17 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.7.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.7.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.