runlot@0.1.0-rc.102
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected callers and data flows do not substantiate the scanner's blocking claims, including at the required agent integration location. The source supports ordinary deployment CLI behavior, with native runtime internals remaining outside this static source assessment.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Explicit user invocation of CLI commands activates the inspected behavior; no npm install hook is present.
Impact
The inspected source establishes no unauthorized agent settings mutation, credential theft, or remote response execution.
Mechanism
The CLI prints MCP setup instructions, authenticates configured API requests, generates validators, and launches a local development runtime.
AI rationale
The inspected callers and data flows do not substantiate the scanner's blocking claims, including at the required agent integration location. The source supports ordinary deployment CLI behavior, with native runtime internals remaining outside this static source assessment.
Network endpoints1
dash.runlot.io
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI with no npm install lifecycle hooks or runtime self-dependency.
- The indicated agent configuration location formats a Cursor configuration path; its explicit MCP install caller prints setup instructions without writing agent settings.
- Saved credentials are selected by API origin, and the active CLI selects credentials for its configured API destination.
- The API client sends requests to its configured base URL and handles responses as data.
- Dynamic evaluation compiles generated schema validators; the inspected source does not execute fetched response code.
- The development launcher supplies application secrets to a local runtime child process.
Evidence against
- The shipped native runtime's internal behavior is outside the inspected JavaScript source.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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 {
...
L978: * hostname (the original request went there), and the server derives the org
L979: * and project names from it. Doing `location.replace` with the `redirect` that
L980: * 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 {
...
L978: * hostname (the original request went there), and the server derives the org
L979: * and project names from it. Doing `location.replace` with the `redirect` that
L980: * 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.102.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.102 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.