oh-my-codex@0.21.31
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior, but global postinstall can acquire a native executable automatically, so residual lifecycle risk remains. Agent configuration locations inspected were test fixtures or read-only discovery, not install-time mutation.
Decision evidence
public snapshot- The postinstall hook runs only for global installs; local installs return without work.
- A global install automatically hydrates a native runtime from release assets, creating a lifecycle-time executable acquisition path.
- The downloaded archive is checked against the release manifest’s size and SHA-256 before extraction and caching.
- Native agent files are generated under user or project Codex directories, while agent management is exposed through explicit CLI commands.
- The inspected agent configuration target locations are test fixtures or read-only configuration discovery.
- The source inspected here does not establish credential collection, unrelated data transfer, consumer policy changes, or unconsented agent configuration mutation.
Source & flagged code
11 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.31.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.31 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.