oh-my-opencode@5.1.29
The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe scanner hints led to package-specific setup, QA fixtures, test code, and bundled runtime behavior on inspection. The lifecycle hook’s cache cleanup is limited to this package’s plugin names, and no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json confirms the registry install hook only runs postinstall.mjs; the executable also has prepare and build hooks.
- postinstall checks platform binaries and removes cached directories only when their names begin with this package’s two plugin names.
- The QA target scripts describe disposable Codex/OpenCode environments, and the CLI runtime-copy code only copies bundled MCP files when matching source arguments exist.
- The flagged probe, browser runtime, terminal bundle, LSP implementation, cancellation test, and smoke test show test, bundled-library, or LSP process-management context; no concrete attack behavior was established in the inspected excerpts.
- The bundled archive downloader fetches an archive and writes it to a cache path; the inspected flow validates archive entries before extraction.
Source & flagged code
23 flaggedSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
package.jsonView on unpkg · L1Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to oh-my-opencode@5.1.29.
See all versions of oh-my-opencode for other recorded verdicts.
- Review the evidence and your use of oh-my-opencode@5.1.29 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.