runlot@0.1.0-rc.142
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and source inspection found credentials bound to the selected API origin with MCP setup exposed as an explicit command or configuration snippet. Scanner hints for credential exfiltration and remote code execution were not supported by the inspected behavior.
Decision evidence
public snapshot- package.json defines build, test, and typecheck scripts, with no install lifecycle hook.
- Saved credentials are selected by the API origin; login saves credentials for the selected API.
- MCP setup is an explicit CLI command or configuration snippet; the indicated target describes a Cursor configuration path.
- MCP requests send the bearer token to the selected API URL.
- The default API is dash.runlot.io; no unrelated credential recipient or confirmed attack was identified.
Source & flagged code
10 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L44Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L44Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.142.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.142 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.