runlot@0.1.0-rc.89
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is a user-invoked deploy CLI with no install lifecycle. The indicated agent-config code only prints setup instructions for an explicit mcp install command and does not write foreign agent files.
Decision evidence
public snapshot- package.json exposes the runlot CLI bin and only build, test, and typecheck scripts, with no preinstall, install, or postinstall hook and no runtime self-dependency.
- The flagged agent helper returns display strings for Claude Code, Cursor, and Claude Desktop config paths and a suggested MCP JSON snippet.
- runlot mcp install validates the client name, prints that text with console.log, and returns without writing those agent files.
- The bundle can spawn processes, write project and local config files, and send crash reports to Sentry after a user runs the CLI.
- Those behaviors come from explicit commands or crash handling, not from an npm install hook.
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.89.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.89 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.