Security audit
Security checks for vulnerabilities and agentic risk
The AiVOOV workflow is coherent, but its automatic setup can execute unverified remote code without clear approval or limits on local changes.
Review and approve CLI installation separately, verify the release, and check its automatic skill synchronization settings before use. Requests pass through OOMOL to AiVOOV, and audio creation requires your approval. The complete bundled skill was inspected; the remote installers and resulting local changes could not be verified. No malicious intent was established.
The supplied command performs remote code execution for an apparent OOMOL CLI installation rather than AiVOOV data operations. Nothing in the supplied content establishes this installer as a supporting dependency for AiVOOV. The downloaded script is not supplied, so its additional behavior cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote content with the invoking user's privileges, without inspection, version pinning, or independent integrity verification. A compromised distribution endpoint or malicious installer update could access local secrets or modify the host; the legitimate dependency relationship and missing-CLI condition reduce exposure but do not remove 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 setup instructions direct execution of downloaded shell and PowerShell scripts without explaining that this runs remote code locally or requiring explicit installation approval. Although conditional on the CLI being missing, this expands a request to operate AiVOOV into a potentially consequential host modification without the confirmation required for service writes.
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