socket@1.1.167
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no install lifecycle hook or self-dependency, and the flagged primitives are reachable through its user-invoked CLI and bundled dependencies. Static inspection found no concrete malicious behavior.
Decision evidence
public snapshot- The manifest exposes command-line binaries and contains no automatic install lifecycle hook.
- The launcher starts the packaged CLI only when the user invokes a command.
- The flagged dynamic evaluation is terminfo formatting compilation in bundled terminal code.
- The flagged environment access only enables semver debug logging.
- The vendor bundle defines the package-aligned Socket API base URL.
- The CLI analytics function calls the Socket SDK for an explicitly selected command.
- The binary artifact is a Maven extension JAR with standard metadata.
- No preinstall, install, or postinstall script is declared.
- No self-dependency is declared.
- No source evidence shows credential collection or unconsented exfiltration.
- No confirmed persistence, destructive action, or broad configuration 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.167.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.167 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.