socket@1.1.163
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThere is no concrete malicious install-time or automatic behavior, but the opaque executable JAR prevents a clean verdict under the required source-only review. The observed command execution is user-invoked and package-aligned.
Decision evidence
public snapshot- The package ships an opaque Maven extension JAR, so its compiled classes cannot be fully assessed from JavaScript source.
- The user-invoked CLI launches the bundled JavaScript command with inherited environment variables.
- The bundled CLI can write analysis sidecar data and invoke external build-analysis tooling.
- A vendored terminal library dynamically compiles generated terminal-formatting code.
- package.json has no preinstall, install, or postinstall hook.
- The executable is activated through the declared socket command, not during installation or import.
- The inspected CLI file writes a temporary analysis sidecar and explicitly disables Coana report submission.
- The flagged registry file is a bundled dependency implementation; inspection found no concrete credential upload in the reviewed portions.
- No self-dependency, persistence mechanism, or broad agent-control-surface mutation was found.
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 socket@1.1.163.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@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.