Security audit
Security checks for vulnerabilities and agentic risk
The CodeRabbit workflow requires approval for account changes, but its setup fallback directs the agent to run a remote installer without a separate approval check.
Review the setup fallback before installing. Prefer installing a reviewed CLI version yourself and require approval before any downloaded installer runs. OOMOL will handle your connected CodeRabbit credentials and requests. Keep the existing confirmation checks for role, seat, and other account changes. The supplied static scan reported no findings, but the remote installer and service implementation were not included for inspection.
The supplied command executes a remotely hosted Oomol installation script, with no demonstrated connection to CodeRabbit. This accesses an inconsistent resource and introduces an undeclared installation capability, rather than merely implementing the described CodeRabbit functionality. The downloaded script's further behavior cannot be determined from the supplied chunk.
The command pipes mutable network content directly into Bash without a pinned artifact or independent integrity verification; the PowerShell alternative uses the same download-and-execute pattern. If the distribution endpoint or release infrastructure is compromised, attacker-controlled code could run with the invoking account's permissions and access local files or credentials. The legitimate dependency and HTTPS transport reduce suspicion of malicious intent but do not eliminate this supply-chain risk.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
When the CLI is missing, the skill directs the agent to execute a remote installer without first explaining local system changes or obtaining installation-specific approval. A request to operate CodeRabbit does not necessarily authorize running arbitrary installation code on the user's machine, although the conditional fallback limits when this occurs.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources