runlot@0.1.0-rc.154
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe agent configuration and credential findings resolve to ordinary user-invoked setup and credentials scoped to the selected API origin. The bundled native runtime is executed with secrets but its behavior remains unverified, so the package cannot be cleared or blocked from this inspection.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the CLI and declares only build, test, and typecheck scripts; it has no install lifecycle hook.
- The agent setup target names an MCP config path, while `mcp install` prints instructions and returns without writing that configuration.
- Saved credentials are selected by matching the requested API origin.
- The `dev` path starts the packaged runtime with project configuration and secrets in its environment.
- The offline analysis identifies the packaged ELF runtime but cannot analyze its behavior.
- The inspected `mcp install` path only prints setup instructions.
- The credential lookup uses the selected API origin.
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.154.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.154 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.