runlot@0.1.0-rc.178
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe scanner flags resolve to normal CLI behavior: login stores a session for the selected API, while crash reporting is disclosed and can be disabled. I found no evidence of credential theft or unrelated command-output exfiltration.
Decision evidence
public snapshot- The manifest exposes a CLI and declares no install lifecycle hooks.
- The default API is https://dash.runlot.io; a different API is selected through an explicit --api flag or RUNLOT_API_URL setting.
- Credentials are saved after the explicit login command and associated with the selected API origin.
- Crash reports are disclosed, can be disabled with RUNLOT_TELEMETRY=0, and command arguments and secrets are described as stripped before sending.
- The flagged process execution supports CLI build and project tasks; I found no evidence that it sends command output to an unrelated host.
- The credential flow uses a Runlot session returned by the selected API; I found no fixed unofficial credential gateway.
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 · L4288Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.178.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.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.