runlot@0.1.0-rc.175
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe entrypoint is a CLI with no install hooks. Review of the flagged flows found credentials scoped to the configured API origin and disclosed, opt-out crash telemetry with argument scrubbing; the reported exfiltration and remote-execution chain was not established.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and declares no install lifecycle hooks.
- Credentials are selected and saved by the API origin, keeping tokens scoped to the chosen service.
- The CLI sends its token as a bearer credential to the configured API URL.
- Crash-report telemetry drops unrecognized command arguments and provides an opt-out.
- The CLI discloses crash reporting, says arguments and secrets are stripped, and explains how to disable it.
- The source sends crash reports to a fixed Sentry ingestion endpoint, but the reports are disclosed runtime telemetry with scrubbing and an opt-out.
- The scanner's dynamic-evaluation indicator also matches bundled schema-validator code generation; no remote-response execution chain was identified.
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.175.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.175 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.