runlot@0.1.0-rc.157
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install hook, and the agent setup command only prints instructions. The inspected network behavior is disclosed, opt-out crash reporting to a fixed package telemetry endpoint, with command arguments and secret-like values scrubbed.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A non-API error occurs while running the CLI, with telemetry enabled by default unless disabled through supported settings.
Impact
Crash details may be reported for debugging, but the inspected source does not show credential theft, remote code execution, or automatic agent configuration changes.
Mechanism
The CLI sends scrubbed command and error metadata to Sentry; its MCP install subcommand only prints setup guidance.
AI rationale
The manifest has no install hook, and the agent setup command only prints instructions. The inspected network behavior is disclosed, opt-out crash reporting to a fixed package telemetry endpoint, with command arguments and secret-like values scrubbed.
Network endpoints1
o4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and lists only build, test, and typecheck scripts; it has no install lifecycle hook.
- The MCP install command prints setup instructions and a configuration path; it does not write agent configuration.
- The runtime sends reports only for non-API errors. Reports go to the fixed Sentry endpoint, and telemetry can be disabled with RUNLOT_TELEMETRY or DO_NOT_TRACK.
- The CLI notice describes crash reporting and says command arguments and secrets are stripped 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.157.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.157 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.