@socketsecurity/cli-with-sentry@1.1.168
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 install-time attack or confirmed exfiltration was found. However, the user-triggered execution of an opaque bundled Maven extension prevents a clean source-only verdict.
Decision evidence
public snapshot- When invoked on a Maven project, the CLI loads a bundled JAR into Maven as an extension, so opaque bytecode executes in the project's Maven process.
- The bundled Maven extension is binary bytecode and could not be source-reviewed.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- The binary extension is reached through the CLI's Maven-manifest path, not package installation.
- The terminal library's dynamic Function use compiles terminal capability strings and is not evidence of exfiltration.
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.168.
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.168 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.