@socketsecurity/cli@1.1.171
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source shows normal user-invoked CLI and Maven-extension behavior but leaves an executable bundled archive outside source-level verification. This warrants a warning rather than a block because no automatic installation trigger or concrete attack was found.
Decision evidence
public snapshot- The user-invoked Maven manifest path loads a bundled Java archive into Maven.
- The CLI launches a child process with the caller environment.
- Bundled terminal code dynamically constructs functions.
- Bundled dependencies include child-process and HTTP client primitives.
- package.json has no preinstall, install, or postinstall hook.
- The archive is reached from an explicit Maven manifest command, not package installation.
- No concrete credential theft, stealth persistence, or destructive behavior was established from inspected source.
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.171.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.171 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.