runlot@0.1.0-rc.182
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks, and the entrypoint’s credential handling is scoped to the configured API origin. Crash telemetry is disclosed, can be disabled, and scrubs command arguments; the routing hints do not establish exfiltration or remote code execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Crash telemetry runs after qualifying CLI errors; credentials are used when a CLI command contacts its configured API.
Impact
No malicious impact identified; crash metadata may be sent to the listed telemetry endpoint unless telemetry is disabled.
Mechanism
Credentials are selected and saved by API origin. Crash reports send scrubbed error, stack, and command metadata to Sentry.
AI rationale
The manifest has no install hooks, and the entrypoint’s credential handling is scoped to the configured API origin. Crash telemetry is disclosed, can be disabled, and scrubs command arguments; the routing hints do not establish exfiltration or remote code execution.
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 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entrypoint and has no install lifecycle hooks.
- Credentials are stored and selected by API origin; the API defaults to dash.runlot.io and an alternate URL requires an explicit RUNLOT_API_URL setting.
- Crash reports are sent only for qualifying errors; command arguments are scrubbed, and the CLI discloses the reports and provides an opt-out.
- The package’s subprocess and dynamic-code references occur in bundled build/runtime and schema-validation code; no attack behavior was identified in those paths.
Evidence against
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);
...
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.182.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.182 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.