runlot@0.1.0-rc.189
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest and source show a deployment and database CLI with credentials scoped to the selected API origin. The scanner's network and command-execution flags are consistent with those functions; crash telemetry is disclosed, scrubbed, and opt-out.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
CLI invocation; crash reporting occurs only after an unexpected error.
Impact
No unauthorized credential transfer, command-output exfiltration, or remote code execution was identified.
Mechanism
Credentials are chosen for the configured API origin. Crash diagnostics go to Sentry and can be disabled with RUNLOT_TELEMETRY=0.
AI rationale
The manifest and source show a deployment and database CLI with credentials scoped to the selected API origin. The scanner's network and command-execution flags are consistent with those functions; crash telemetry is disclosed, scrubbed, and opt-out.
Evidence
${RUNLOT_CONFIG} or ~/.runlot/credentials.json~/.runlot/telemetry-notice
Network endpoints2
dash.runlot.ioo4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and declares no install lifecycle hooks.
- The default API is dash.runlot.io, and saved credentials are selected by API origin.
- Crash reports are sent only for unexpected errors; the CLI scrubs report fields, discloses the reporting, and provides a RUNLOT_TELEMETRY=0 opt-out.
Evidence against
- Crash telemetry is enabled by default and sends exception messages, stack traces, and scrubbed command information to Sentry when an unexpected error occurs.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
11 flaggeddist/index.jsView file
6const __filename = __runlotFilePath(import.meta.url);
L7: const __dirname = __runlotDirname(__filename);
L8: var __create = Object.create;
...
L47: // ../../packages/api/src/index.ts
L48: function base64urlJson(v) {
L49: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L54: function gitQuery(ref, path) {
L55: const q = new URLSearchParams();
L56: if (ref !== "") q.set("ref", ref);
...
L129: async request(method, path, init) {
L130: const res = await fetch(new URL(path, this.opts.baseUrl), {
L131: ...init,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L64298});
L4299: readFromStdout(stdout);
L4300: afterClose(null);
...
L4308: let worker = new worker_threads2.Worker(__filename, {
L4309: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L4310: transferList: [workerPort],
L4311: // From node's documentation: https://nodejs.org/api/worker_threads.html
L4312: //
L4313: // Take care when launching worker threads from preload scripts (scripts loaded
L4314: // and run using the `-r` command line flag). Unless the `execArgv` option is
L4315: // explicitly set, new Worker threads automatically inherit the command line flags
Critical
Command Output Exfiltration
Source executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L4298Findings
4 Critical5 High5 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalCommand Output 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
HighTrigger Reachable Credential Exfiltrationdist/index.js
HighTrigger Reachable Command Output Exfiltrationdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.189.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.189 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.