Security audit
Security checks for vulnerabilities and agentic risk
The certificate-reading workflow is coherent, but setup can execute unverified downloaded software without a separate approval step.
Review and approve CLI installation separately before allowing setup to run. Use a verified release and a read-only Venafi connection, and consider whether OOMOL should handle your credentials and certificate data. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent automatic skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Installer and backend effects remain partly unverified.
The supplied command performs remote code execution from an Oomol-hosted installation endpoint. The declared purpose does not mention software installation or establish any relationship between Oomol and Venafi TLS Protect Datacenter. No Venafi search or read operation is shown. The downloaded script's contents and any further effects are not available for assessment.
Piping a network-fetched script directly into Bash executes its contents with the agent process's privileges without a pinned version, integrity verification, or review. Compromise of the installer distribution could allow theft of locally accessible credentials or modification of the host; HTTPS and the legitimate OOMOL setup context do not eliminate 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 missing-CLI recovery workflow directs the agent to execute remote installers without explaining the host-level effects or requiring explicit installation approval. Although setup is conditional and serves a legitimate purpose, a read-oriented Venafi request can thereby expand into local software installation; this overlaps with the external-script execution finding.
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