Security audit
Security checks for vulnerabilities and agentic risk
The contract workflow has sensible safeguards, but setup can execute unverified remote software without a clear approval step.
Review the setup behavior before installing. Prefer a separately reviewed, fixed CLI release and require approval before running downloaded installers. The CLI documents an OO_SKILLS_SYNC_DISABLED control for preventing automatic skill writes in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL will mediate access to contract data and credentials. Only the Markdown skill was bundled; the live installer contents could not be verified.
The command executes an external installation script from cli.oomol.com, with no demonstrated connection to eSignatures.com. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence that the CLI supports the declared purpose. The remote script's contents and any further effects are not available for assessment.
Piping a live HTTPS download directly into bash executes remotely supplied code without pinning a version or independently verifying the artifact; the PowerShell alternative has the same issue. Compromise of the installation endpoint or its delivery infrastructure could execute attacker-controlled commands with the invoking user's permissions, potentially exposing local files and credentials. The domain is relevant to the documented tool, but that does 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 fallback workflow directs installation of downloaded executable code without explicitly requiring user approval for local software installation or explaining its system effects. Although conditional and relevant to the task, this can expand a service-data request into local code execution and environment changes that the user did not authorize.
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