runlot@0.1.0-rc.105
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source does not substantiate the scanner's malicious labels: agent setup prints instructions, authentication selects origin-scoped credentials, and evaluation compiles validators. No concrete malicious chain was established by static inspection.
Decision evidence
public snapshot- package.json has no installation lifecycle hooks or runtime self-dependency; its CLI entrypoint is dist/index.js.
- The flagged agent configuration location returns a display path. Its caller formats instructions, and the explicit MCP install command only prints them.
- Saved credentials are selected by API origin. Callers select credentials for the configured destination before the API client sends authenticated requests; RUNLOT_TOKEN is caller-supplied.
- Dynamic evaluation compiles generated schema validators; the inspected dynamic import resolves a local framework build module.
- Bundled runtime selection and child processes support explicitly invoked local development and browser login.
- Crash reporting supports opt-out and scrubs diagnostic text and command arguments before sending 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.105.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.105 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.