Security audit
Security checks for vulnerabilities and agentic risk
The data-reading functions fit the stated purpose, but setup can execute unchecked downloaded code and introduce additional agent skills without clear user control.
Review and install a verified CLI release yourself before allowing setup. Consider the buyer and purchase data available through your connected account. To prevent additional agent skills from being installed automatically, upstream documents OO_SKILLS_SYNC_DISABLED=1. The remote installers and hosted connector implementation remain unverified; no bundled malicious payload was found.
The supplied chunk performs remote installer execution, not the declared Digistore24 data access. Although installation can support a skill, nothing in this chunk establishes that the Oomol installer is a required Digistore24 dependency. The downloaded script's further behavior is not visible and cannot be determined from this code.
The command executes the current contents of a remote installation script immediately, without pinning or independently verifying the downloaded artifact. HTTPS protects transport but does not protect against a compromised publisher or hosting endpoint, which could supply code capable of accessing local files and credentials with the user's privileges.
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 pipe remote content directly into Bash or PowerShell without an integrity-verification step or explicit installation approval. If the installation endpoint or delivery infrastructure is compromised, an otherwise read-only data request could lead to arbitrary code execution with the invoking user's privileges; the missing-CLI condition limits exposure but does not prevent exploitation.
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