Security audit
Security checks for vulnerabilities and agentic risk
The Label Studio workflow is coherent, but its setup fallback executes downloaded code without verification or an explicit approval step.
Review and approve CLI installation separately before allowing setup to run. Prefer a verified, fixed release, and review its automatic skill-installation settings. OOMOL will mediate access to your connected Label Studio account; confirm project-creation and task-creation payloads. The bundled instructions were fully reviewed, but remote installer and connector behavior remain unverified.
The supplied chunk performs remote installer execution rather than Label Studio operations. Nothing supplied establishes the Oomol CLI installation as a supporting requirement for the declared functionality. The downloaded script is not provided, so its further behavior and system effects cannot be determined.
The command pipes a mutable HTTPS response directly into Bash without verifying a pinned version, signature, or trusted digest. Compromise of the distribution endpoint could therefore execute attacker-controlled code with the invoking user's privileges; the PowerShell alternative has the same weakness.
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 fallback directs the agent to install software by executing downloaded scripts without requiring informed approval for code execution or system changes. Although limited to a missing CLI, this expands a Label Studio data task into host-level execution and could expose local credentials and files if the installer or its distribution channel is compromised.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Label Studio homepage: https://labelstud.io
- API documentation: https://api.labelstud.io/api-reference/introduction/getting-started