runlot@0.1.0-rc.155
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe inspected source supports ordinary CLI login and user-directed MCP setup, with saved credentials scoped to the selected API origin. The scanner hints do not establish credential exfiltration or an active attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI runs when a user invokes it; MCP setup is an explicit subcommand that prints setup instructions.
Impact
No unrelated credential disclosure or unconsented agent configuration change was established.
Mechanism
Login and MCP use credentials selected for the chosen API origin. MCP setup prints a configuration snippet for the user to add.
AI rationale
The inspected source supports ordinary CLI login and user-directed MCP setup, with saved credentials scoped to the selected API origin. The scanner hints do not establish credential exfiltration or an active attack.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and lists build, test, and typecheck scripts; it has no install lifecycle hook.
- Saved credentials are selected by API origin, and a saved default token is used only when its stored origin matches the requested API.
- Login builds its browser URL from the selected API address; MCP setup prints a configuration snippet for the user to add.
- MCP server startup uses the selected API address and its matching credentials.
Evidence against
- The inspected source shows no credential transfer to an unrelated recipient or automatic agent configuration change.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 flaggeddist/index.jsView file
43// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L97: async request(method, path, init) {
L98: const res = await fetch(new URL(path, this.opts.baseUrl), {
L99: ...init,
...
L1108: * hostname (the original request went there), and the server derives the org
L1109: * and project names from it. Doing `location.replace` with the `redirect` that
L1110: * 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 · L4343// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L97: async request(method, path, init) {
L98: const res = await fetch(new URL(path, this.opts.baseUrl), {
L99: ...init,
...
L1108: * hostname (the original request went there), and the server derives the org
L1109: * and project names from it. Doing `location.replace` with the `redirect` that
L1110: * 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 · L43Findings
3 Critical5 High7 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
MediumSecret Patterndist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Affected versions and remediation
This report applies to runlot@0.1.0-rc.155.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.155 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.