Security audit
Security checks for vulnerabilities and agentic risk
The location searches fit the stated purpose, but setup can execute unverified software and introduce broader agent changes without clear user approval.
Review and approve CLI installation separately before enabling automatic setup. Consider disabling startup skill synchronization using OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Only submit locations you intend to share through OOMOL with HERE. The remote installers and hosted connector implementation were not independently verified; the review found no evidence of malicious intent.
The supplied command performs remote code execution for an apparent CLI installation rather than searching or reading HERE data. Nothing in the supplied chunk establishes that this installation is a supporting implementation detail of the declared functionality. The downloaded script's further behavior cannot be determined from this chunk.
The supplied chunk only initiates login; it contains no HERE search or data-reading operation. Authentication could support a declared service, but the chunk does not establish that oo authenticates to HERE. Its demonstrated behavior therefore differs materially from the declared purpose.
The setup command pipes a mutable remote script directly into Bash without integrity verification or an inspection step; the PowerShell alternative has the same issue. Compromise of the distribution endpoint could execute arbitrary code with the invoking user's privileges, and although installation is conditional on a missing CLI, it expands a read-oriented task into local code execution without explicit installation approval.
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 workflow instructs the agent to execute HERE searches through OOMOL, including actions that accept addresses and latitude/longitude coordinates. Labeling all read actions as safe to run directly overlooks disclosure of potentially sensitive location data; the file identifies the services but provides no privacy warning.
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