Security audit
Security checks for vulnerabilities and agentic risk
The Paperform reads match the advertised purpose, but setup can execute downloaded software without clear user approval.
Review the setup before installing. Prefer a separately reviewed, version-pinned CLI installation and require approval before running downloaded installers. Consider disabling automatic skill synchronization using the documented OO_SKILLS_SYNC_DISABLED setting. OOMOL mediates access to your Paperform data; external installer behavior remains unverified. No malicious behavior was established.
The supplied command performs remote software installation rather than searching or reading Paperform data. Although dependency installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Paperform functionality. The downloaded script's contents and further effects are not available for assessment.
Piping a remotely fetched script directly into bash executes whatever the endpoint returns with the invoking user's privileges, without a pinned version or independent integrity verification. Compromise of the installer distribution path could therefore expose local files and credentials or enable persistent system changes; the legitimate dependency and conditional setup trigger reduce exposure but do not remove this 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 instructs an agent to execute downloaded installation scripts without first explaining that this runs external code and can modify the local environment. Although restricted to a missing-CLI error, installation is a materially different operation from reading Paperform data and warrants separate user authorization.
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