Security audit
Security checks for vulnerabilities and agentic risk
The Gumroad workflow has clear safeguards, but setup directs the agent to execute unverified remote installers without explicit user approval.
Review is warranted for automatic setup, not evidence of malicious intent. Install a verified CLI release yourself or explicitly approve installation after reviewing its local changes, including agent-skill synchronization. OOMOL mediates access to your Gumroad data; retain the required confirmations for refunds and other writes. Remote installer behavior remains unverified.
The supplied code executes an Oomol-hosted installer rather than performing the declared Gumroad data operations. Nothing in the chunk establishes this installation as a supporting dependency for Gumroad access. The downloaded script's contents and further effects cannot be determined from the supplied code.
Piping a live HTTPS response directly into Bash executes remote code without a pinned version or independently verified integrity; the PowerShell alternative has the same weakness. Compromise of the installer distribution path could yield arbitrary execution with the invoking user's privileges, although the snippet alone does not establish malicious installer behavior or that execution occurred.
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 directs installation of executable software after a missing-command error without requiring approval for local system changes. Although limited to first-time setup and apparently intended to install a legitimate dependency, this expands a Gumroad task into local code execution and could expose accessible files and credentials if the installer is compromised.
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