runlot@0.1.0-rc.176
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source does not substantiate the flagged credential redirection, command-output exfiltration, or remote-code execution. The CLI includes disclosed, opt-out crash telemetry and otherwise uses credentials for the matching API origin.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the runlot CLI and declares no install lifecycle scripts.
- Credentials from the config file are used only when its API origin matches the selected API origin; the default API is dash.runlot.io.
- The detected new Function call compiles generated schema-validation code, not code from a remote response.
- Crash reports are sent to Sentry only for qualifying errors; the CLI discloses the reports and provides RUNLOT_TELEMETRY=0 to disable them.
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.176.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.176 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.