Security audit
Security checks for vulnerabilities and agentic risk
The Dixa features fit their purpose, but setup can execute downloaded code and make lasting agent changes without clearly requiring your approval.
Review the setup before installing. Prefer a reviewed, version-pinned CLI installation, and require approval before an ordinary Dixa request triggers software installation. Review automatic bundled-skill synchronization and grant only necessary Dixa access. OOMOL mediates customer-data access; remote installers and hosted connector internals remain unverified.
The supplied code contains only a remote-script execution command and no Dixa search or read operations. Although installing a dependency can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Dixa functionality. The downloaded script's contents and downstream effects are not provided and cannot be determined.
Piping a live HTTPS response directly into Bash executes unverified remote code with the invoking user's permissions. Compromise of the installer delivery infrastructure could expose local files and credentials or permit persistent changes; the legitimate dependency context and conditional fallback reduce exposure but do not establish code integrity.
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 installation of software without explicitly obtaining approval for executing remote code or changing the local environment. Although this is a legitimate dependency setup step and only occurs after a missing-command error, a request to read Dixa data does not by itself authorize local software installation.
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