socket@1.1.153
CLI for Socket.dev
AI Security Review
scanned 3mo ago · by lpm-firewall-aiScanner hits are explained by a security CLI’s user-invoked subprocess/network features and bundled third-party code. Source inspection found no lifecycle hook or concrete malicious chain.
Decision evidence
public snapshot- CLI can modify shell completion/aliases, but only through explicit commands and prompts.
- Bundled JAR is a Maven extension archive with named Coana/Maven classes.
- package.json has no preinstall, install, postinstall, or prepare hook.
- bin/cli.js only launches the packaged CLI after user invokes a bin command.
- libnpmpack.js is vendored npm/pacote-style registry and Git helper code; its env uses are runtime configuration, not a package-specific credential upload.
- No confirmed AI-agent config writes, stealth persistence, destructive behavior, or unconsented install-time mutation.
Source & flagged code
15 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.153.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.153 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.