Security audit
Security checks for vulnerabilities and agentic risk
The npm features fit their purpose, but a missing dependency can trigger execution of an unverified online installer without separate user approval.
Review the dependency setup before use. Install an independently verified CLI release yourself and require approval before the agent runs downloaded installers. Consider OOMOL's credential handling, npm permissions, and billing. The bundled text shows no credential theft or destructive behavior, but the external installer and hosted service remain unverified.
The fallback setup expands a read-oriented npm task into downloading and executing an installer, without requiring explicit approval for local system changes. Installing the disclosed connector is a legitimate dependency rather than evidence of malicious purpose, but a missing CLI can trigger unverified remote code execution with the agent process's privileges.
The supplied command performs authentication rather than the declared npm search/read operations. Nothing in the chunk establishes that this login is a supporting step for npm access. The command alone does not establish which service is authenticated or how credentials are handled.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `audit_package_versions` — Get npm security advisories for requested exact package versions.
- `get_current_user` — Get the npm username associated with the connected access token.
- `get_package` — Get a compact summary and version list for an npm package.
- `get_package_download_counts` — Get download totals for up to 128 npm packages over an inclusive period.
- `get_package_download_trend` — Get daily download counts for one npm package over an inclusive period.
Piping the HTTPS response directly into Bash executes whatever the installer endpoint serves with the current process's privileges. HTTPS protects transport but does not establish that the script is an approved, immutable release, so endpoint or release-pipeline compromise could lead to local code execution and data theft.
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
Both setup examples execute downloaded code immediately, without an integrity check or explicit approval for installation and system changes. The missing-command prerequisite limits when this occurs, but it does not protect against a compromised installer endpoint or an unexpectedly invasive installer.
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