Security audit
Security checks for vulnerabilities and agentic risk
A Cochrane reading request can trigger software installation without a clear approval step.
Review the setup behavior before installing. Use an independently verified, pinned CLI installation and require approval before any fallback installer runs. Consider the CLI's bundled-skill installation and OOMOL account access. The package shows no credential theft or destructive intent, but its external installer and hosted implementation remain outside the inspected artifact.
The fallback expands a Cochrane read request into downloading and executing an installer that can modify the local system, without requiring explicit user approval. Installing a connector dependency is a legitimate operational purpose, but it does not justify implicitly authorizing remote code execution; this overlaps with the installer findings below.
The supplied chunk only initiates authentication; it contains no Cochrane search or reading behavior and does not establish that the login supports Cochrane access. Its demonstrated purpose therefore differs materially from the declared purpose. The command alone does not establish credential theft or data exfiltration.
The command pipes a mutable remote script directly into Bash without a pinned version or independent integrity verification. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying code that accesses local files, credentials, or other resources available to the executing account.
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 instructions direct the agent to execute downloaded shell or PowerShell code without an explicit consent checkpoint or disclosure of local system changes. Although conditional on a missing dependency, following these instructions can execute compromised installer content with the agent process's permissions.
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