runlot@0.1.0-rc.169
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected CLI source shows ordinary error reporting and development-runtime selection, but it also launches a shipped native executable whose behavior remains unresolved. That material gap prevents a clean verdict, while the inspected source does not establish a concrete attack.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the runlot CLI and includes a bin directory.
- The CLI resolves a platform-specific runlot-dev-runtime and starts it as a child process.
- The supplied offline analysis identifies the shipped executable as an unsupported artifact and says its behavior remains unresolved.
- The inspected JavaScript reports filtered CLI errors to Sentry; the report path has telemetry opt-outs and is called for non-API errors.
- The inspected JavaScript ties the reviewed Sentry request to CLI error reporting; it does not establish credential theft or another concrete attack.
Source & flagged code
11 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L6Source executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L4288Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.169.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.169 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.