runlot@0.1.0-rc.183
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential, command-output and dynamic-execution behaviors resolve to origin-bound CLI authentication, local command history and bundled schema validation. Runtime crash reporting is disclosed, strips command arguments and secrets, and can be disabled.
Decision evidence
public snapshot- The manifest exposes the CLI at dist/index.js and has no install lifecycle hook; its scripts are build, test and typecheck.
- Stored credentials are selected by API origin, and the login flow saves a token for the API chosen by that explicit command.
- Crash reporting sends scrubbed exception and stack details to Sentry; the CLI discloses this reporting and provides RUNLOT_TELEMETRY=0 to disable it.
- Command arguments are scrubbed before reporting, while captured stderr is stored in a local commands.json ring buffer.
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.183.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.183 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.