runlot@0.1.0-rc.145
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe bundle's dynamic function construction is schema-validator code generation, while MCP setup is an explicit command that only prints instructions. Credential routing and crash telemetry are consistent with the CLI's stated operation; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json exposes a CLI and lists only build, test, and typecheck scripts; it has no install lifecycle hook.
- Saved credentials are associated with an API origin, and API requests send them to that API's configured base URL.
- The indicated MCP configuration code resolves known client config paths; `runlot mcp install` prints setup text and returns instead of editing those files.
- Crash reporting runs only for enabled, recognized crashes; it scrubs known secret patterns and posts the error report to Sentry.
- The `new Function` call is in bundled schema-validator code generation, not a remote-response execution path.
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.145.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.145 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.