runlot@0.1.0-rc.141
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest exposes a CLI without install hooks, and the inspected MCP setup path prints configuration rather than writing it. The credential flow ties saved credentials to the selected API origin and sends them to that selected API.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user runs the CLI or explicitly invokes `runlot mcp install <client>`.
Impact
No automatic agent configuration mutation or unrelated credential forwarding was established.
Mechanism
The setup command prints an MCP server snippet; when the server is run, it authenticates requests to the configured or default Runlot API with a matching token.
AI rationale
The manifest exposes a CLI without install hooks, and the inspected MCP setup path prints configuration rather than writing it. The credential flow ties saved credentials to the selected API origin and sends them to that selected API.
Evidence
package.jsondist/index.js
Network endpoints1
dash.runlot.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/index.js as the CLI entrypoint and declares no install lifecycle hooks.
- The indicated MCP configuration code only returns configuration paths; the MCP setup command prints a snippet for the user to apply.
- The snippet configures the MCP server to run `runlot mcp`.
- The MCP server selects the configured or default Runlot API and requires a matching token before starting.
- Requests send the token to the selected API URL; saved credentials are keyed by API origin.
Evidence against
- The inspected entrypoint code shows no automatic MCP configuration write or hidden credential redirect.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
10 flaggeddist/index.jsView file
44function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * comes back is the caller's job.
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L4444function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * comes back is the caller's job.
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L44Findings
3 Critical5 High5 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalRemote Response Code Executiondist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighEvaldist/index.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.141.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.141 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.