runlot@0.1.0-rc.123
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source does not support the scanner's malicious labels: the flagged agent location only supplies printed setup instructions, and the evaluation and credential flows serve package operations. No concrete malicious chain was established by static inspection.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Explicit CLI commands activate service and development operations; qualifying errors activate optional crash reporting.
Impact
No confirmed credential theft, remote response execution, or automatic agent configuration mutation was established.
Mechanism
Saved credentials are scoped by service origin, validators compile generated code, and agent configuration paths appear in printed instructions.
AI rationale
The inspected source does not support the scanner's malicious labels: the flagged agent location only supplies printed setup instructions, and the evaluation and credential flows serve package operations. No concrete malicious chain was established by static inspection.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares a CLI, no install lifecycle hooks, and no runtime self-dependency.
- Saved credentials are selected by API origin; login obtains and saves credentials for the selected service.
- The flagged Cursor configuration path builds setup text. The explicit MCP install command prints that text and returns without modifying agent configuration.
- Dynamic evaluation compiles generated schema validators. Fetched documentation is cached and returned as text.
- Crash reporting supports disabling and scrubs exception text and command arguments.
- The development server passes project secrets to a locally resolved runtime child process.
Evidence against
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.123.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.123 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.