@socketsecurity/cli-with-sentry@1.1.153
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner findings resolve to expected CLI subprocess handling, vendored package-manager code, an inspectable Maven archive, and explicit Sentry/Socket telemetry. No lifecycle hook, secret exfiltration path, remote payload execution, or persistence behavior was found.
Decision evidence
public snapshot- package.json has no preinstall/install/postinstall lifecycle hook.
- bin/cli.js only launches the packaged CLI after explicit CLI invocation.
- dist/instrument-with-sentry.js initializes the declared Sentry integration.
- dist/utils.js telemetry is org-scoped, disabled by default, and redacts token-like argv values.
- external/blessed/lib/tput.js eval is terminal-capability parsing in vendored blessed code.
- The JAR is a structured Maven extension archive, not an opaque executable payload.
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 @socketsecurity/cli-with-sentry@1.1.153.
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.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.