runlot@0.1.0-rc.147
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install hook, and the reviewed auth path binds saved credentials to the selected API origin. The indicated MCP helper only prints optional setup instructions; no credential theft or agent configuration mutation was established.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and build, test, and typecheck scripts; it defines no install lifecycle hook.
- Credentials are selected and saved by the API server's origin, and login uses the selected API URL.
- The indicated agent configuration paths are displayed as setup guidance; the MCP install command prints instructions and returns without editing those files.
Source & flagged code
12 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L43Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L43Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.147.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.147 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.