runlot@0.1.0-rc.185
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI sends default-on crash telemetry to Sentry, while its disclosure notice only appears when stderr is a TTY. The arguments are scrubbed and the reviewed code does not establish credential exfiltration, so this warrants a warning for undisclosed runtime telemetry in non-TTY use.
Decision evidence
public snapshot- The CLI entry point is dist/index.js, where crash reporting is reachable at runtime.
- Crash reports are sent to the fixed Sentry endpoint at o4512108816105473.ingest.us.sentry.io.
- Reports include exception details, stack traces, command metadata, runtime version, and platform.
- Telemetry is enabled by default, but its notice is skipped when stderr is not a TTY.
- Command arguments are reduced to recognized flags and command names; other values are redacted.
- The notice describes anonymous crash reports and provides RUNLOT_TELEMETRY=0 as an opt-out.
- Credentials are selected for the configured API origin, and the reviewed code did not establish credential forwarding to Sentry.
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 · L4298Findings
Affected versions and remediation
This report applies to runlot@0.1.0-rc.185.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.185 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.