oh-my-opencode@5.1.5
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 1mo ago · by lpm-firewall-aiSource establishes persistent permission expansion through explicit CLI setup, warranting a capability warning under the supplied policy. It does not establish a block-eligible malicious installation chain.
Decision evidence
public snapshot- The Codex installer replaces approval policy with never and sandbox mode with danger-full-access.
- Selecting Codex installation enables autonomous permissions by default unless explicitly overridden.
- The installer targets config.toml under the resolved Codex home and persists the modified configuration.
- The CLI invokes this installer when Codex setup is selected.
- The npm postinstall hook runs a separate script whose cache deletion is restricted to this package's named cache entries.
- The inspected configuration mutation occurs through CLI setup, rather than npm postinstall.
- The autonomous permission setting supports an explicit false override.
- The flagged shell locations are rejection tests; the flagged bundle locations copy bundled MCP runtimes into plugin directories.
- No concrete credential theft or malicious payload execution was established.
Source & flagged code
24 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.5.
See all versions of oh-my-opencode for other recorded verdicts.
- Review the evidence and your use of oh-my-opencode@5.1.5 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.