Security audit
Security checks for vulnerabilities and agentic risk
The Pipedream features fit the stated purpose, but the setup instructions can automatically execute unverified installers and introduce broader agent changes.
Review and verify the CLI installation separately before allowing the agent to run the setup fallback. Check its automatic skill synchronization settings and connect only the intended Pipedream account through OOMOL. The bundled instructions show no malicious behavior, but the remote installers and hosted connector implementation were not verified.
The supplied command performs remote script execution for an apparent Oomol CLI installation and shows no Pipedream search or read functionality. Nothing in the supplied material establishes this installation as a supporting dependency for the declared purpose. The downloaded script's contents and further effects are unknown.
The supplied chunk only performs a CLI login and contains no Pipedream-specific operation or indication that this login supports Pipedream access. Authentication could be a supporting implementation detail in a broader workflow, but the provided code does not establish that connection.
Piping the HTTPS installer directly into bash executes mutable remote content with the invoking account's privileges, without an opportunity to verify or review it first. HTTPS protects transport but does not protect against a compromised distribution server or malicious installer update; the legitimate dependency context reduces suspicion of malicious intent, not the execution 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 setup fallback directs the agent to execute downloaded shell or PowerShell code without prior inspection, integrity verification, or explicit approval for software installation. Although conditional on a missing CLI, this turns an ordinary read request into local code execution; a compromised installer could access files and credentials available to the invoking account.
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