runlot@0.1.0-rc.106
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiDirect inspection resolves the strongest scanner hints to printed MCP setup instructions, origin-scoped authentication, schema compilation and local application execution. No concrete malicious chain or warning-worthy agent configuration operation was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Users invoke CLI commands; no npm install lifecycle hook is defined.
Impact
No concrete credential theft, remote payload execution or automatic agent configuration mutation was established.
Mechanism
Agent configuration paths are displayed without writes, stored credentials are scoped by API origin, and generated code implements schema validation.
AI rationale
Direct inspection resolves the strongest scanner hints to printed MCP setup instructions, origin-scoped authentication, schema compilation and local application execution. No concrete malicious chain or warning-worthy agent configuration operation was established.
Network endpoints2
dash.runlot.ioo4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hooks or runtime self-dependency.
- The indicated Cursor configuration path is returned as text; the explicit MCP install command prints instructions and returns without modifying agent configuration.
- Saved credentials are selected by API origin; login obtains and saves credentials for the selected service.
- Dynamic evaluation compiles schema validators; inspected remote responses are consumed as text rather than executed.
- The development command passes project secrets to its local application runtime.
- Crash reporting redacts secret patterns and supports disabling telemetry.
Evidence against
- The shipped native development runtime's internals were not established by JavaScript source inspection.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
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.106.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.106 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.