runlot@0.1.0-rc.135
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found no install hook or concrete malicious behavior. The flagged dynamic function construction is in bundled schema-validation code, while MCP configuration setup is explicit and credential lookup is origin-scoped.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI and defines no install lifecycle hook.
- The indicated MCP configuration code only reports a configuration path; the install subcommand prints setup instructions for a user to apply.
- Credentials loaded from the saved login file are selected by API origin, limiting them to the origin they belong to.
- The MCP setup is an explicit subcommand, and the source inspected does not establish an attack surface.
- The bundle contains dynamic function construction in its bundled schema-validation code, but inspection did not show it executing remotely supplied code.
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.135.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.135 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.