runlot@0.1.0-rc.180
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe main concern is default-on runtime crash telemetry to Sentry: it sends scrubbed exception details and stacks without an explicit per-run prompt, so I classify it as suspicious telemetry. The flagged credential-redirection concern is not supported by the inspected credential flow, which scopes stored tokens to the selected API origin.
Decision evidence
public snapshot- Crash telemetry is enabled by default and can be disabled with RUNLOT_TELEMETRY or DO_NOT_TRACK.
- On reportable errors, the CLI sends a Sentry event to o4512108816105473.ingest.us.sentry.io.
- The event includes scrubbed error messages and stacks, command metadata, and tags; arbitrary error details may still be sent.
- The manifest has no install lifecycle hook; its executable is the CLI at dist/index.js.
- Stored credentials are selected by matching the configured API origin, and login saves credentials for that API.
- Telemetry redacts common secret patterns and home-directory paths, and provides opt-out environment variables.
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.180.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.180 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.