oh-my-codex@0.21.9
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection supports a package-aligned Codex CLI with explicit setup and a global-install-only native runtime hydration step. The flagged eval process is fixture-driven, and the inspected evidence does not establish malicious behavior.
Decision evidence
public snapshot- The manifest limits its postinstall to dispatching a local script; that script does nothing for local installs and hydrates the runtime only for global installs.
- The setup module is the package’s explicit setup command and installs Codex-related assets and configuration.
- The flagged eval collector launches Codex through npx as part of fixture collection; its source does not establish install-time execution.
- The flagged test and configuration locations concern Codex paths, agent setup, auth storage, plugin configuration, or local binary paths; the inspected excerpts do not show an attack.
- No concrete credential exfiltration, stealth persistence, destructive behavior, or unconsented broad control-surface mutation was established.
- The package has a postinstall lifecycle hook, and global installs may hydrate a native runtime binary.
- The setup command writes agent-related configuration, but it is reached through explicit setup and the examined source shows overwrite guards or user scope handling.
Source & flagged code
12 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.9.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.9 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.