oh-my-codex@0.21.17
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe scanner’s lifecycle and agent-configuration indicators map to ordinary package behavior: postinstall does not invoke setup, local installs are a no-op, and native hydration is version-matched and checksum-checked. The reviewed source did not establish an attack surface.
Decision evidence
public snapshot- package.json runs a postinstall hook, but dist/scripts/postinstall.js exits for local installs; on global installs it may hydrate the matching native runtime and update an install-version stamp.
- Native runtime downloads resolve to the package repository’s release assets, validate the release manifest and archive checksum, and are limited to supported platform and architecture combinations.
- The flagged setup code is reached through the CLI command; the postinstall hook does not call setup. The inspected required runtime and test paths did not establish an attack.
- Global postinstall can fetch a native binary and write a user install stamp.
- Native release URL configuration accepts an environment override, and manifest and archive integrity checks use the downloaded manifest.
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.17.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.17 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.