runlot@0.1.0-rc.124
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 29d ago · by lpm-firewall-aiInspected source does not substantiate the scanner's malicious behavior claims: saved credentials are origin-bound, agent setup prints instructions, and dynamic evaluation generates schema validators. The remaining capabilities align with user-invoked deployment and local development operations.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Users invoke CLI commands; no automatic installation hook is present.
Impact
No covert credential export, remote response execution, or automatic agent configuration mutation was established.
Mechanism
API requests use selected credentials, schema validation uses generated code, and development commands load local runtime components.
AI rationale
Inspected source does not substantiate the scanner's malicious behavior claims: saved credentials are origin-bound, agent setup prints instructions, and dynamic evaluation generates schema validators. The remaining capabilities align with user-invoked deployment and local development operations.
Network endpoints3
dash.runlot.iodocs.runlot.ioo4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no automatic installation lifecycle hooks or runtime self-dependency.
- The flagged agent configuration location formats paths; the explicit MCP installation command only prints setup instructions.
- Saved credentials are selected by API origin, including an origin check for legacy tokens.
- Dynamic evaluation compiles generated schema validation code; inspected remote responses are handled as data.
- Crash telemetry scrubs exception text and command arguments before sending reports.
Evidence against
- The CLI includes native development runtimes and network, subprocess, and dynamic loading capabilities; these alone do not establish malicious behavior.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
10 flaggeddist/index.jsView file
44function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * 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 · L4444function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * comes back is the caller's job.
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L44Findings
3 Critical5 High5 Medium5 Low
CriticalCredential 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
HighCommand Output Exfiltrationdist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.124.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.124 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.