Security audit
Security checks for vulnerabilities and agentic risk
The OnceHub features fit the stated purpose, but setup can execute downloaded software without a clear approval or verification step.
Review setup before use. Prefer manually installing a verified, pinned CLI release and explicitly approving local changes. Review its automatic agent-skill synchronization controls. Connect only the OnceHub account and permissions you need, understanding that OOMOL mediates access. The remote installers and live backend were not verified; the inspected artifact does not establish malicious intent.
The supplied command contains no OnceHub access or search/read functionality. Instead, it executes an external installation script. No connection between this installer and the declared OnceHub functionality is established in the supplied chunk, making this a material purpose and resource mismatch. The remote script's further behavior cannot be determined from this command alone.
The command pipes a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative uses the same download-and-execute pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could run with the invoking user's access, although the legitimate setup context provides no evidence of malicious intent.
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 missing-CLI fallback instructs installation without first explaining local system changes or requiring user approval, extending a read-only data request into local software execution. Restricting this fallback to a command-not-found error reduces exposure, but does not establish authorization to modify the environment.
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