runlot@0.1.0-rc.186
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe reported credential-routing concern is not supported by the reviewed code: stored credentials are selected by API origin, with the default API at dash.runlot.io. The CLI does send disclosed, scrubbed crash reports to Sentry with an opt-out; this does not meet the stated criteria for malicious or suspicious telemetry.
Decision evidence
public snapshot- The package exposes dist/index.js as the runlot CLI and describes itself as a deployment and PostgreSQL management tool.
- The default API is https://dash.runlot.io; saved credentials are selected by API origin, so credentials stored for one origin are not automatically reused for another.
- Crash reports are limited to classified errors, and the CLI discloses the reports, says command arguments and secrets are stripped, and provides an opt-out.
- The CLI sends crash reports to a fixed Sentry endpoint when reporting is enabled.
- The bundle includes subprocess and dynamic-code facilities, though the reviewed matches are consistent with bundled tooling and CLI functions.
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.186.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.186 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.