oh-my-codex@0.21.21
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe inspected sources show a default-enabled project plugin execution capability, but no evidence that the package installs a malicious plugin or that its install hook mutates agent configuration. This warrants a warning for the conditional extension risk.
Decision evidence
public snapshot- Hook dispatch is enabled by default unless disabled, and native or derived events can force it on.
- The dispatcher discovers project hook plugins and the runner imports each plugin module before calling its event handler.
- The npm postinstall hook delegates to a script that skips local installs; global installs hydrate the native runtime.
- Agent setup is dispatched through the explicit CLI setup command.
- The inspected lifecycle source describes runtime hydration and install-stamp handling, not hook-plugin creation or agent setup.
- The plugin loader discovers files in the project’s .omx/hooks directory; the inspected sources do not show the package creating plugins there.
Source & flagged code
13 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to oh-my-codex@0.21.21.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.21 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.