@socketsecurity/cli-with-sentry@1.1.178
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiReadable source shows user-invoked CLI execution and fixed Sentry telemetry, but the mandatory binary JAR cannot be cited as required for a clean verdict. A complete source-grounded clean decision is therefore not possible in this pass.
Decision evidence
public snapshot- The manifest exposes command-line entrypoints rather than an install lifecycle hook.
- The CLI launcher runs the packaged CLI after a user invokes a command.
- The Sentry build initializes enabled error reporting to a fixed Sentry ingestion endpoint.
- The required Maven extension JAR is binary and contains no inspectable printable UTF-8 excerpt, preventing the required clean citation coverage.
Source & flagged code
17 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.178.
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.178 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.