runlot@0.1.0-rc.140
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged agent integration only prints setup guidance when explicitly invoked. Credentials are selected in relation to the API origin, so the scanner hints do not establish credential theft or another concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI through dist/index.js and declares no install lifecycle hook.
- The flagged agent integration returns configuration guidance for selected MCP clients; it does not itself write their configuration.
- MCP service startup obtains credentials for the selected API URL and requires a token before starting.
- Stored credentials are selected by matching the API origin, while the default API is the package's own service.
- The CLI supports an explicit API URL override, so a caller can direct credentials they supply to a chosen endpoint.
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.140.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.140 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.