Security audit
Security checks for vulnerabilities and agentic risk
Review recommended: Apple Notary operations are scoped, but setup can run downloaded software whose broader system changes are not explained.
Review or preinstall a pinned CLI before enabling automatic setup, and check its agent-skill installation and synchronization settings. Connecting Apple Notary trusts OOMOL with account access. Keep approval of exact submission payloads enabled. Installer contents and hosted connector internals were unavailable for inspection; this Review verdict reflects setup scope and uncertainty, not evidence of malware.
The supplied code performs remote script execution, not an Apple Notary operation. Although installing tooling could be a supporting implementation detail, the supplied content establishes no connection between this installer and the declared service. The downloaded script's contents and any resulting system changes are not visible in the provided chunk.
The curl-to-bash command executes mutable remote content without pinning a version or verifying a signature or trusted checksum. HTTPS protects transport but does not prevent a compromised distribution server or release pipeline from supplying code that steals accessible credentials or modifies local files; the PowerShell setup command has the same weakness.
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
On a missing-CLI error, the setup instructions direct the agent to execute a remote installer without first obtaining approval for local code execution and system changes. Although this is a conditional dependency-installation step rather than malicious behavior, following it could run attacker-controlled code with the agent's local privileges if the installer distribution is compromised; the declared Bash tool restriction may limit execution in some environments.
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