@socketsecurity/cli-with-sentry@1.1.169
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo lifecycle hook, self-dependency, persistence, or hidden install-time behavior was found. The opaque executable JAR is deliberately invoked against a user project, so this release warrants a warning rather than a clean decision.
Decision evidence
public snapshot- A user-invoked Maven analysis loads the shipped Java archive as a Maven extension; the archive is executable bytecode and was not fully source-inspectable.
- The CLI uploads selected manifest files during a reachability scan to Socket's API.
- package.json defines command-line binaries but no preinstall, install, postinstall, or prepare lifecycle hook.
- The Node launch wrapper only starts the package CLI with the user's arguments.
- The reported eval is terminal-capability compilation in bundled blessed code, not a hidden payload.
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 @socketsecurity/cli-with-sentry@1.1.169.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.1.169 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.