runlot@0.1.0-rc.156
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged agent integration only prints instructions after an explicit command. The reported dynamic evaluation is schema-validator generation; the inspected source did not establish remote-response execution or credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI runs; agent setup guidance is shown only after a user invokes `runlot mcp install`.
Impact
No unconsented agent configuration change, credential transfer to an unrelated recipient, or remote code execution was established.
Mechanism
The setup command prints configuration text, while the MCP server uses credentials associated with its configured API origin.
AI rationale
The manifest has no install hook, and the flagged agent integration only prints instructions after an explicit command. The reported dynamic evaluation is schema-validator generation; the inspected source did not establish remote-response execution or credential exfiltration.
Evidence
package.jsondist/index.js
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entrypoint and lists build, test, and typecheck scripts; it has no install lifecycle hook.
- The flagged agent configuration path is only printed as setup guidance when the explicit `runlot mcp install` command is invoked; that branch does not write configuration files.
- The MCP server uses a credential selected for the configured API origin, and asks the user to log in to that API or supply a token when none is available.
- The dynamic code generation is used to compile schema validators, not to execute code from a remote response.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 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 · L4343// ../../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
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L43Findings
3 Critical5 High7 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
MediumSecret Patterndist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Affected versions and remediation
This report applies to runlot@0.1.0-rc.156.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.156 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.