socket@1.2.1
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a user-invoked Socket CLI and no install-time hook, credential harvesting, persistence, or agent-control mutation. The reviewed behavior is consistent with a security CLI.
Decision evidence
public snapshot- The manifest exposes CLI binaries and its scripts shown are build-related; no automatic install lifecycle hook was found.
- The CLI launcher starts the bundled CLI with the caller's arguments only when the command is invoked.
- Login asks interactively for a Socket API token before configuring the client.
- The inspected required bundled paths, including the Maven archive, showed no package-specific attack behavior.
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 socket@1.2.1.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.2.1 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.