oh-my-opencode@5.1.14
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 supports a warning for explicit agent configuration changes that substantially weaken execution safeguards. It does not substantiate the scanner's malicious verdict or a publish-blocking attack chain.
Decision evidence
public snapshot- The explicit CLI installer invokes Codex setup when Codex is selected.
- Codex autonomous mode defaults to enabled unless explicitly overridden.
- Autonomous setup sets approval_policy to never and sandbox_mode to danger-full-access, removes network restrictions, and hides the full-access warning.
- The installer writes these settings to Codex config.toml and enables package plugins, trusted hooks, and agent configurations.
- The npm postinstall hook performs platform checks and package-specific cache cleanup; inspected source does not establish an automatic agent configuration attack.
- The configuration mutation occurs through explicit CLI setup, with an option to preserve existing permission settings.
- Flagged agent configuration script locations are rejection-test inputs, and the inspected dynamic execution sink in dist/index.js compiles schema validation code.
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.14.
See all versions of oh-my-opencode for other recorded verdicts.
- Review the evidence and your use of oh-my-opencode@5.1.14 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.