runlot@0.1.0-rc.144
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The scanner's agent configuration hint resolves to printed setup guidance, and credential lookup is scoped by API origin.
Decision evidence
public snapshot- package.json exposes a CLI and lists only build, test, and typecheck scripts; it has no install lifecycle hook.
- The flagged agent configuration location supplies a path for setup text. The explicit MCP install command prints that text.
- Saved credentials are selected by API origin, and the API client sends the token to its configured base URL.
- Crash reporting is gated by telemetry settings and non-API errors; the report uses scrubbed error data and is sent to Sentry.
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.144.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.144 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.