runlot@0.1.0-rc.133
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook, and the reviewed MCP setup subcommand prints instructions rather than mutating agent configuration. Credentials are selected by API origin; the inspected code does not show them being sent to an unrelated destination.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI entrypoint and declares no install lifecycle hook.
- The indicated agent configuration code resolves paths for Cursor and Claude Desktop; it does not write configuration.
- The MCP install subcommand prints setup instructions only when explicitly invoked.
- Credentials are selected by API origin, and MCP setup explains how the user supplies them to the client.
- The inspected credential and MCP behavior does not establish credential theft, remote code execution, or an install-time attack.
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.133.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.133 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.