Security audit
Security checks for vulnerabilities and agentic risk
The SignPath workflow has clear safeguards, but automatic setup executes unverified downloaded code and leaves broader agent changes unexplained.
Review and install the CLI separately before allowing setup. Its documented automatic skill synchronization can be disabled using OO_SKILLS_SYNC_DISABLED=1; see the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL brokers the SignPath connection, so use appropriately scoped credentials and review each signing payload. The remote installer and hosted service were not verified.
The supplied code performs remote installer execution, with no visible SignPath integration or data operations. Nothing provided establishes this installer as a supporting dependency for SignPath, so its behavior and accessed resource materially differ from the declared purpose. The remote script's further behavior cannot be determined from this chunk.
The command immediately executes a mutable remote script without checking a pinned version, trusted signature, or independently obtained digest; the PowerShell alternative has the same issue. If the distribution endpoint or delivery pipeline is compromised, attacker-controlled code could run with the invoking user's privileges and access local files or credentials; HTTPS and the legitimate dependency context do not eliminate that 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 flow instructs an agent to install software after a command-not-found error without requiring explicit approval for executing remote code or changing the local system. This is a separate authorization boundary from running SignPath actions, although the conditional setup and openly documented dependency reduce suspicion of malicious intent.
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