runlot@0.1.0-rc.150
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. Scanner flags correspond to explicit API configuration, printed MCP setup instructions, generated schema validation code, and conditional crash reporting.
Decision evidence
public snapshot- The manifest routes the CLI to dist/index.js and lists only build, test, and typecheck scripts; it has no install lifecycle hook.
- The MCP helper names client configuration locations and prints setup instructions; its install subcommand prints the snippet rather than writing configuration.
- Login uses the selected API origin for browser handoff, and saved credentials are looked up by API origin.
- API requests send the token as a bearer credential to the configured API base URL.
- The flagged new Function call compiles generated schema validators in bundled validation code.
- Crash reporting is limited to enabled crash errors, scrubs report text, and sends the report to the package’s Sentry endpoint.
Source & flagged code
12 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L43Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L43Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.150.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.150 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.