runlot@0.1.0-rc.103
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource inspection resolves the scanner hints through ordinary CLI authentication, schema compilation, local development runtime selection and scrubbed crash reporting. The flagged agent integration and its caller only print setup instructions, leaving no concrete malicious behavior established.
Decision evidence
public snapshot- package.json exposes a CLI without automatic installation hooks or a runtime self-dependency.
- The flagged Cursor configuration path is returned as setup text; the explicit MCP install command prints instructions without writing agent configuration.
- Saved credentials are selected by API origin, including legacy credentials; MCP resolves credentials for its selected API endpoint.
- Dynamic evaluation compiles generated schema validators; the inspected flow does not execute remote response code.
- The development runtime loader selects a local platform binary for development functionality.
- Crash telemetry scrubs exception text, stacks and command arguments before sending reports and supports disabling collection.
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.103.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.103 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.