runlot@0.1.0-rc.190
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s automatic crash reporting sends exception messages, stacks, and command arguments to Sentry by default, which is undisclosed runtime telemetry carrying identifying details. The reviewed credential lookup is scoped to the configured API origin, and I found no support for the scanner’s alleged credential redirection or remote code execution.
Decision evidence
public snapshot- The `runlot` CLI is exposed through `dist/index.js`.
- Runtime error reporting is enabled by default unless `RUNLOT_TELEMETRY` or `DO_NOT_TRACK` disables it.
- On eligible errors, the report includes exception messages and stacks plus scrubbed command arguments, then sends them to Sentry.
- The CLI invokes this reporting path automatically for non-API errors.
- Saved Runlot credentials are selected by matching their API origin to the configured API URL.
- The package describes itself as a CLI for deploying apps and managing PostgreSQL, consistent with its command execution and network activity.
Source & flagged code
11 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L6Source executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L4298Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.190.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.190 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.