runlot@0.1.0-rc.158
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or confirmed attack behavior. Crash reporting is opt-out and scrubs common secrets and most command arguments; agent setup is explicit and prints instructions rather than mutating configuration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A non-API command error triggers crash reporting unless telemetry is disabled; agent setup text is printed only when the user invokes the install subcommand.
Impact
Crash diagnostics leave the machine; no malicious action or unconsented agent configuration change was established.
Mechanism
Crash details and filtered command arguments are posted to the configured Sentry project. The agent install command prints configuration instructions rather than writing agent files.
AI rationale
Source inspection found no install lifecycle hook or confirmed attack behavior. Crash reporting is opt-out and scrubs common secrets and most command arguments; agent setup is explicit and prints instructions rather than mutating configuration.
Evidence
package.jsondist/index.js
Network endpoints1
o4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points the runlot command to dist/index.js and declares no lifecycle hook.
- The agent configuration code describes setup text and paths; the install subcommand prints that text when explicitly invoked.
- Crash reports are sent only for non-API errors, and telemetry can be disabled with RUNLOT_TELEMETRY or DO_NOT_TRACK.
- The report code scrubs common credential patterns, home paths, and most command arguments before sending.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
13 flaggeddist/index.jsView file
43// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L109: async request(method, path, init) {
L110: const res = await fetch(new URL(path, this.opts.baseUrl), {
L111: ...init,
...
L1144: * hostname (the original request went there), and the server derives the org
L1145: * and project names from it. Doing `location.replace` with the `redirect` that
L1146: * comes back is the caller's job.
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L433553});
L3554: readFromStdout(stdout);
L3555: afterClose(null);
...
L3563: let worker = new worker_threads2.Worker(__filename, {
L3564: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L3565: transferList: [workerPort],
L3566: // From node's documentation: https://nodejs.org/api/worker_threads.html
L3567: //
L3568: // Take care when launching worker threads from preload scripts (scripts loaded
L3569: // and run using the `-r` command line flag). Unless the `execArgv` option is
L3570: // 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 · L3553Findings
4 Critical5 High7 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
MediumSecret Patterndist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
Affected versions and remediation
This report applies to runlot@0.1.0-rc.158.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.158 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.