Security audit
Security checks for vulnerabilities and agentic risk
The Retable workflow controls data changes, but setup can run downloaded code and introduce additional agent skills without clear approval.
Review the CLI installation before allowing automatic setup. Prefer a reviewed version and decide whether it may install additional agent skills; current [CLI documentation](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) provides OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization. Use narrowly scoped Retable access and retain the required approvals for writes and deletions. The remote installer payload was unavailable for inspection, so its full local effects remain uncertain.
The supplied chunk performs no visible Retable operations and instead executes an installer from a different service. Nothing supplied establishes this installer as a supporting dependency for Retable. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The command streams a mutable remote script directly into Bash without an independently verified digest, signature, or pinned version. Compromise of the distribution endpoint or release pipeline could therefore execute attacker-controlled code with the invoking user's permissions; HTTPS and the legitimate CLI dependency 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
The missing-CLI fallback directs execution of downloaded shell or PowerShell scripts without requiring informed approval for local software installation. Although conditional and relevant to the workflow, this expands a Retable data task into local code execution and system changes that the user may not have authorized.
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