runlot@0.1.0-rc.177
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI’s credential flow is scoped to the selected API origin, and its error reporting is disclosed with an opt-out and scrubbing of arguments and secrets. The flagged dynamic code construction is part of AJV’s schema validator, and I found no malicious credential or command-output exfiltration chain.
Decision evidence
public snapshot- The package exposes a CLI entry point and declares no install lifecycle scripts.
- Runlot credentials are selected by API origin, preventing credentials for one origin from being used for another.
- Crash reports are disclosed to users, can be disabled, and strip command arguments and secrets before sending.
- Crash reporting runs on CLI errors; the bundle’s dynamic function construction is AJV schema-validator code generation.
- The CLI reads its own RUNLOT_TOKEN or credentials file to authenticate with its configured Runlot API.
- The CLI sends scrubbed crash reports to a Sentry endpoint.
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.177.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.177 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.