runlot@0.1.0-rc.129
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install hook or automatic agent configuration change. Login credentials are associated with the selected API origin, and the flagged MCP setup path only prints instructions.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI runs when a user invokes it; MCP setup output requires the user to run the install subcommand.
Impact
No harmful impact was established from the inspected behavior.
Mechanism
The reviewed MCP install path prints configuration guidance and does not mutate agent configuration or transfer credentials.
AI rationale
Source inspection found no install hook or automatic agent configuration change. Login credentials are associated with the selected API origin, and the flagged MCP setup path only prints instructions.
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 a CLI and lists only build, test, and typecheck scripts; it has no install lifecycle hook.
- The MCP install command prints setup instructions, and the inspected configuration path is displayed as text rather than written by that command.
- Login uses the selected API URL, and saved credentials are looked up by that API's origin.
Evidence against
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.129.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.129 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.