registry / runlot
runlot
runlot CLI — deploy apps and manage PostgreSQL
This report shows the evidence for runlot@0.1.0-rc.191. 0 of 78 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe CLI routes saved credentials to the API origin selected for login or through its configured API URL; the reviewed source shows no fixed unofficial gateway or hidden credential redirect. Its crash reporting is disclosed, opt-out, and associated with runtime errors, while the other flagged capabilities serve the CLI's build and validation functions.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User-invoked CLI commands make API requests; eligible runtime errors can trigger crash reporting.
Impact
No unrelated credential transfer, command-output exfiltration, or concealed remote code execution was found.
Mechanism
The CLI sends bearer credentials to the selected API origin, stores credentials by origin, and sends disclosed crash reports to Sentry with an opt-out.
AI rationale
The CLI routes saved credentials to the API origin selected for login or through its configured API URL; the reviewed source shows no fixed unofficial gateway or hidden credential redirect. Its crash reporting is disclosed, opt-out, and associated with runtime errors, while the other flagged capabilities serve the CLI's build and validation functions.
Evidence
~/.runlot/credentials.json~/.runlot/telemetry-notice
Network endpoints2
dash.runlot.ioo4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes `dist/index.js` as the CLI and declares no install lifecycle hooks.
- The default API is `https://dash.runlot.io`; credentials are stored and selected by API origin.
- Login saves the token for the API the user chose, and requests send it as a bearer token to that API.
- Crash reports are disclosed as anonymous, with arguments and secrets stripped and an opt-out setting.
- Crash reporting is reached from the CLI error handler, not from an install hook.
Evidence against
- The CLI uses network requests and handles login credentials as part of its deployment and account-management purpose.
- The bundle contains child-process execution for esbuild tooling and dynamic code generation for schema validation.
- The CLI sends crash reports to a Sentry endpoint when eligible runtime errors occur.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.191.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of runlot@0.1.0-rc.191 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.