runlot@0.1.0-rc.126
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe manifest points to a CLI and has no install hook. Inspected credential handling scopes saved credentials by API origin, while agent setup is presented for explicit user configuration; the scanner hints do not establish a malicious attack path.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI or manually configures its MCP server in an agent.
Impact
The inspected behavior does not establish credential forwarding to an unrelated destination or automatic agent configuration mutation.
Mechanism
The CLI uses origin-matched saved credentials for API requests; MCP setup is presented as configuration for the user to add.
AI rationale
The manifest points to a CLI and has no install hook. Inspected credential handling scopes saved credentials by API origin, while agent setup is presented for explicit user configuration; the scanner hints do not establish a malicious attack path.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI entrypoint and declares no install lifecycle hook in its manifest.
- The MCP integration is emitted as setup configuration for a user to add, rather than being written automatically during package installation.
- Saved credentials are selected by matching the requested API origin; MCP requests send the selected token to that API URL.
Evidence against
- No confirmed malicious behavior was identified in the inspected entrypoint, credential handling, or MCP setup path.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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.126.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.126 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.