runlot@0.1.0-rc.174
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed entrypoint behavior fits a deployment and database CLI: credentials are scoped to the selected API origin, and crash reporting is disclosed with an opt-out. Scanner alerts about command execution and dynamic evaluation resolve to ordinary bundled tooling and Ajv schema code generation.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Users invoke CLI commands; crash reporting runs for reportable command errors when telemetry is enabled.
Impact
No unauthorized credential forwarding or unrelated command execution was identified.
Mechanism
The CLI reads credentials for the selected API origin and sends crash reports to its configured Sentry endpoint. The dynamic function call is Ajv schema code generation.
AI rationale
The reviewed entrypoint behavior fits a deployment and database CLI: credentials are scoped to the selected API origin, and crash reporting is disclosed with an opt-out. Scanner alerts about command execution and dynamic evaluation resolve to ordinary bundled tooling and Ajv schema code generation.
Evidence
~/.runlot/credentials.json (or the path set by RUNLOT_CONFIG)telemetry-notice in the credentials directory
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 `runlot` CLI entrypoint.
- Credentials are read from the Runlot config file and associated with an API origin; the default API is `https://dash.runlot.io`.
- Crash reports are sent to the Sentry endpoint only for reportable errors; the CLI says it strips command arguments and secrets and provides `RUNLOT_TELEMETRY=0` to disable reporting.
- The `new Function` call is in Ajv's schema validator code generation, not an execution path for remote responses.
Evidence against
- The CLI sends runtime crash reports to Sentry, including exception details and stack data, though it discloses this and provides an opt-out.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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);
...
L126: async request(method, path, init) {
L127: const res = await fetch(new URL(path, this.opts.baseUrl), {
L128: ...init,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L64288});
L4289: readFromStdout(stdout);
L4290: afterClose(null);
...
L4298: let worker = new worker_threads2.Worker(__filename, {
L4299: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L4300: transferList: [workerPort],
L4301: // From node's documentation: https://nodejs.org/api/worker_threads.html
L4302: //
L4303: // Take care when launching worker threads from preload scripts (scripts loaded
L4304: // and run using the `-r` command line flag). Unless the `execArgv` option is
L4305: // 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 · L4288Findings
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.174.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.174 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.