runlot@0.1.0-rc.137
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe inspected source does not substantiate the scanner’s claims of credential exfiltration or remote response execution. The agent configuration path is user-directed setup, and credentials are scoped to the selected API origin.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI; MCP configuration instructions require the user to invoke the install subcommand and apply the printed setup.
Impact
The inspected behavior supports the package’s deployment CLI and optional agent integration; it does not establish credential forwarding to an unrelated recipient or an unconsented configuration write.
Mechanism
The MCP server selects a token for the configured API origin, while the install subcommand prints a server configuration snippet. Crash telemetry uses a fixed Sentry endpoint and can be disabled through environment settings.
AI rationale
The inspected source does not substantiate the scanner’s claims of credential exfiltration or remote response execution. The agent configuration path is user-directed setup, and credentials are scoped to the selected API origin.
Network endpoints1
o4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the CLI through dist/index.js and declares no install lifecycle hook.
- The flagged agent configuration location only identifies a Cursor MCP configuration path; the install subcommand prints suggested configuration rather than writing it.
- Credentials are selected by API origin, and the MCP server uses the selected API URL for its bearer token.
- Crash telemetry has an opt-out and sends to the package’s Sentry endpoint.
Evidence against
- The bundled CLI includes environment access, network requests, dynamic loading references, and native runtime files, but inspected paths did not establish credential theft or remote code execution.
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.137.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.137 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.