runlot@0.1.0-rc.151
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no install hook or confirmed attack behavior. The scanner's credential and MCP concerns are resolved by origin-scoped saved credentials and an explicit command that prints configuration without writing it.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI and lists build, test, and typecheck scripts, with no install hook.
- dist/index.js sends bearer tokens to the configured API base URL; the default API is dash.runlot.io.
- Saved credentials are selected by API origin, and login obtains a token through a browser handoff from that API.
- The MCP configuration targets are inspected; the explicit `runlot mcp install` command prints configuration text rather than writing agent configuration.
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.151.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.151 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.