Security audit
Security checks for vulnerabilities and agentic risk
The Northbeam reads are appropriately scoped, but setup can execute downloaded software without verification or separate approval.
Review the setup before installing. Use a separately reviewed CLI release, approve its local changes, and connect only the intended Northbeam account. Consider disabling startup skill synchronization using the publisher-documented OO_SKILLS_SYNC_DISABLED setting. Remote installer behavior remains unverified; the artifact does not establish malicious intent. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied command performs remote installer execution, not Northbeam data access. Nothing in the provided chunk establishes that this installation is a supporting dependency for the declared purpose. The downloaded script's contents and further effects are not available for assessment.
The command pipes a mutable network response directly into Bash without verifying an independently trusted signature or digest; the PowerShell example uses the same download-and-execute pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the invoking user's privileges, potentially exposing local credentials and files. HTTPS and the conditional setup path reduce some exposure but do not establish artifact integrity.
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
A missing CLI triggers instructions to execute a remote installer without explaining its privileges or system changes, or requiring explicit approval. Although this is a conditional prerequisite rather than routine behavior, it can expand a read-only data request into software installation; the declared Bash restriction may constrain execution but is not a substitute for installation safeguards.
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