@socketsecurity/cli-with-sentry@1.3.0
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found no lifecycle hooks or concrete malicious behavior. The observed telemetry is associated with user-invoked CLI execution and defaults to disabled.
Decision evidence
public snapshot- Package metadata exposes command-line binaries rather than an install lifecycle hook.
- The command launcher starts the packaged CLI only when the user invokes its binary.
- The terminal capability component identifies itself as terminfo parsing code.
- The large registry component is bundled JavaScript using standard Node modules.
- The CLI records telemetry during an invoked command, while the telemetry configuration defaults to disabled and Sentry capture is conditional on a configured client.
- The bundled archive contains a standard Maven manifest entry.
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.3.0.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.3.0 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.