@socketsecurity/cli@1.1.163
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo automatic install-time attack or concrete exfiltration was found, but the package deliberately executes an opaque bundled Java extension in consumer Maven projects. This is a real unresolved runtime capability, so a warning is appropriate rather than a clean or blocking verdict.
Decision evidence
public snapshot- The CLI bundles opaque Java bytecode and explicitly passes it to Maven as an extension during a user-invoked manifest operation.
- The command launcher starts the bundled CLI in a child process with the caller's environment.
- The package contains dynamic Function construction in bundled terminal-support code.
- The published manifest has command entry points but no install lifecycle hook.
- No preinstall, install, or postinstall script is present.
- The Java extension is activated only through a CLI operation, not automatically on package installation.
- The inspected Java archive manifest contains ordinary Maven build metadata and no network configuration.
- The flagged URL-building code is a bundled dependency utility, not evidence of credential exfiltration.
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.163.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.163 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.