runlot@0.1.0-rc.130
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection found no malicious behavior: there are no install hooks, credential lookup is origin-scoped, and agent setup instructions are produced only by an explicit command. The scanner’s dynamic evaluation match is in bundled schema validation, and crash reporting is gated and sends crash diagnostics to Sentry.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and declares no install lifecycle hook.
- The MCP installer prints setup instructions for an explicitly invoked command; it does not write agent configuration itself.
- Saved credentials are selected by API origin, and requests send the token to the configured API client.
- Crash reporting is gated by telemetry settings and limited to crash events.
- The dynamic function construction is part of bundled schema validation.
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.130.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.130 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.