Security audit
Security checks for vulnerabilities and agentic risk
DeskTime actions have appropriate safeguards, but setup can execute unverified downloaded code without a separate approval step.
Review the setup before installing. Install a verified CLI release yourself and prevent automatic installer execution. Review its managed-skill synchronization settings and authorize only the DeskTime access you need, especially employee tracking data. The remote installers and exact installed release could not be inspected; no malicious behavior was established.
The supplied code contains no DeskTime interaction or evidence that the Oomol installer is a supporting dependency for DeskTime functionality. Its sole visible action is remote installer execution, which materially differs from the declared purpose. The downloaded script's contents and further effects are not available for assessment.
Piping an HTTPS response directly into bash executes mutable remote content without a pinned version or independent integrity verification. Compromise of the installer distribution path could yield arbitrary code execution with the invoking process's permissions; the legitimate vendor relationship and conditional setup reduce suspicion of malicious intent but do not eliminate this supply-chain 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 fallback directs the agent to execute downloaded shell or PowerShell code without explicit approval for installing software or changing the local system. Although installation is relevant and only triggered when the CLI is missing, a compromised installer could execute arbitrary code with the agent's privileges; the declared oo-only Bash allowance may limit execution if enforced.
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