runlot@0.1.0-rc.179
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged process, environment, network, and dynamic-code references resolve to the CLI's local development runtime, API client, and schema validation. Crash reporting sends scrubbed diagnostics to Sentry, is disclosed by the CLI, and can be disabled with RUNLOT_TELEMETRY=0.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Crash telemetry runs when a CLI command fails with a reportable non-API error; authenticated API calls occur during user-invoked commands.
Impact
Crash diagnostics are reported to the package's Sentry project. API credentials go to the selected API service; local worker secrets are available to the local runtime.
Mechanism
The CLI sends scrubbed crash details to Sentry and sends its Runlot token to the selected API origin. Local development starts workerd with configured project secrets.
AI rationale
The flagged process, environment, network, and dynamic-code references resolve to the CLI's local development runtime, API client, and schema validation. Crash reporting sends scrubbed diagnostics to Sentry, is disclosed by the CLI, and can be disabled with RUNLOT_TELEMETRY=0.
Evidence
~/.runlot/credentials.json~/.runlot/telemetry-notice
Network endpoints2
dash.runlot.ioo4512108816105473.ingest.us
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/index.js as the CLI and has no install lifecycle hook.
- The default API is https://dash.runlot.io; credentials are looked up by API origin, and requests send the token to the selected API URL.
- Crash reports contain scrubbed exception details, stack, and command arguments and go to the configured Sentry endpoint; the CLI discloses this telemetry and provides RUNLOT_TELEMETRY=0 to disable it.
- The CLI starts workerd with project secrets in its child environment for local development; this behavior is part of its stated dev-runtime purpose.
Evidence against
- The bundle uses environment variables, child processes, and dynamic evaluation, but the inspected paths fit CLI, build, and local development behavior.
- The package includes a native runtime binary, but the reviewed source uses it to serve the user's local worker.
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);
...
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.179.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.179 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.