runlot@0.1.0-rc.136
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 26d ago · by lpm-firewall-aiInspected source supports a clean verdict: the package has no install lifecycle hook, and its MCP setup is user-directed. Saved credentials are matched to the selected API origin; no credential exfiltration or agent-control mutation was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the runlot CLI or its MCP command.
Impact
No confirmed attack surface was established.
Mechanism
The CLI obtains credentials for the selected API origin; MCP configuration is printed for user setup rather than automatically written.
AI rationale
Inspected source supports a clean verdict: the package has no install lifecycle hook, and its MCP setup is user-directed. Saved credentials are matched to the selected API origin; no credential exfiltration or agent-control mutation was established.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and has no preinstall, install, or postinstall hook.
- The flagged agent-configuration code describes MCP config paths and prints configuration for a user to add; it does not write those files.
- Saved credentials are selected by matching the API origin, and the MCP command requires a token before starting.
Evidence against
- The MCP server supports a caller-selected API URL, but saved credentials are origin-bound and RUNLOT_TOKEN is explicitly supplied through the client environment.
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.136.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.136 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.