Security audit
Security checks for vulnerabilities and agentic risk
The Paddle workflow has clear safeguards, but its automatic setup can execute unchecked remote code and introduce broader agent changes without clear user control.
Review setup before installing. Install a reviewed, fixed CLI release yourself and inspect or disable its managed-skill synchronization rather than allowing the automatic installer fallback. Connect only the intended Paddle account with necessary permissions, understand that OOMOL handles its credentials and requests, and retain approval for business-data changes. The external installers and hosted connector were not verified; no malicious behavior was established in the submitted artifact.
The provided code executes an Oomol-hosted installation script rather than performing the declared Paddle operations. Although dependency installation can be a supporting implementation detail, this chunk establishes no relationship between that installer and Paddle. The remote script's contents are unavailable, so its further effects cannot be determined.
Authentication can support an integration, but the supplied chunk contains no Paddle-specific configuration, resource access, or operations connecting this login to the declared purpose. Its demonstrated behavior is an authentication action, not the advertised Paddle functionality.
Piping a mutable HTTPS installer directly into Bash executes remote content without a prior integrity or authenticity check beyond transport security. Compromise of the distribution endpoint could expose local files and credentials or alter the environment; its legitimate role as CLI setup does not remove that 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 instructs the agent to execute downloaded shell or PowerShell code without requiring informed approval for local installation. A compromised installer source could execute arbitrary commands with the agent's privileges; the missing-CLI condition limits exposure but does not make installation safe.
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