oh-my-codex@0.21.28
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The lifecycle hook’s runtime hydration is package-aligned, while agent and setup configuration changes are dispatched through the explicit CLI setup command.
Decision evidence
public snapshot- package.json invokes the postinstall hook, but dist/scripts/postinstall.js returns immediately for local installs; on global installs it hydrates the package’s native runtime and records the installed version.
- dist/cli/index.js dispatches setup only for the explicit setup command. The inspected setup code writes setup preferences; the postinstall path does not call setup.
- The required runtime and agent integration paths reviewed contain CLI, state, authentication, and configuration behavior; no install-time credential transfer or unconsented broad agent configuration write was established.
- The inspected manifests for the prepared TOML, MCP SDK, and LZMA dependencies have no install lifecycle scripts. The secret-like test data is used in redaction tests.
- The test secret pattern is synthetic redaction-test input, not evidence of a package credential.
- The scanner’s install-time setup concern is not supported by the source: the lifecycle hook does not invoke setup, which is dispatched by the explicit CLI command.
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.28.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.28 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.