runlot@0.1.0-rc.91
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 npm lifecycle hooks. The flagged agent paths are display strings for an explicit mcp install command that only prints setup text.
Decision evidence
public snapshot- package.json exposes only the runlot CLI bin and build, test, and typecheck scripts, with no preinstall, install, or postinstall hook.
- dist/index.js configPath only returns readable path strings for claude-code, cursor, and claude-desktop.
- The runlot mcp install command prints that guidance with console.log and returns without writing agent config files.
- Optional crash reports go to a Sentry ingest host unless RUNLOT_TELEMETRY or DO_NOT_TRACK disables them, and messages are scrubbed before send.
- Local API tokens are read from RUNLOT_TOKEN or ~/.runlot/credentials.json for the configured dash.runlot.io client.
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.91.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.91 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.