socket@1.1.173
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings resolve to a user-invoked CLI, a terminal library's generated formatter, a credential-safe redirect handler, and a Java archive. There is no lifecycle hook or concrete malicious behavior in the inspected sources.
Decision evidence
public snapshot- The manifest exposes command-line binaries and has no install lifecycle hook.
- The command launcher runs the packaged CLI with the user's arguments.
- The flagged dynamic Function use is terminal capability formatting code.
- The registry fetch code removes authorization and cookie headers on a cross-host redirect.
- The bundled CLI makes named Socket SDK API calls, and its API base URL is Socket-owned.
- The JAR finding is a standard Java archive containing named Maven extension classes.
- The package contains command execution and network-capable CLI functionality, but inspection found no automatic activation, credential export, or unrelated recipient.
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.173.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.173 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.