runlot@0.1.0-rc.92
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-airunlot is a user-invoked deploy CLI with no npm lifecycle hooks. The agent-config hint only prints setup text, and the session token is used only against the configured package API.
Decision evidence
public snapshot- package.json exposes only the user-invoked bin runlot at dist/index.js, and its scripts are build, test, and typecheck with no install lifecycle hook.
- configPath returns display strings for Claude Code, Cursor, and Claude Desktop config locations and does not write those files.
- The explicit runlot mcp install command prints installText for a named client and then returns.
- The API origin comes from RUNLOT_API_URL, saved credentials, or https://dash.runlot.io, and the session token is sent only as a Bearer header on fetch requests to that base URL.
- Crash reporting posts a scrubbed stack and command name to a Sentry ingest host unless RUNLOT_TELEMETRY or DO_NOT_TRACK disables it.
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.92.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.92 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.