registry / oh-my-codex / 0.21.2
oh-my-codex@0.21.2
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe scanner’s high-risk hints are not sufficient to establish malicious behavior. Source inspection shows a global-install-gated native hydration hook and agent configuration through an explicit, guarded setup flow, so the remaining concern is a package-owned agent integration capability.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
npm postinstall for a global install; agent setup requires running the CLI setup command.
Impact
No confirmed attack surface was established; the observed agent configuration behavior is guarded and package-aligned.
Mechanism
The hook checks global-install context before doing work. The CLI setup flow provisions package-owned agent configuration and presents a prompt for an AGENTS.md default.
AI rationale
The scanner’s high-risk hints are not sufficient to establish malicious behavior. Source inspection shows a global-install-gated native hydration hook and agent configuration through an explicit, guarded setup flow, so the remaining concern is a package-owned agent integration capability.
Evidence
dist/scripts/postinstall.jsdist/cli/setup.js
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json invokes the postinstall module automatically.
- The postinstall handler returns without work for non-global installs.
- Setup behavior is behind the CLI entrypoint and creates or modifies agent-related configuration during explicit setup.
- Plugin setup asks before enabling a default AGENTS.md configuration.
Evidence against
- The inspected install hook limits its behavior to global installs; no unconsented broad agent-control mutation was established.
- No concrete credential theft, destructive behavior, or dependency-approval expansion was found in the inspected paths.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 flaggedpackage.jsonView file
•scripts.postinstall = node -e "const fs=require('fs');const p='./dist/scripts/postinstall.js';if(fs.existsSync(p))import(p).then(m=>m.main?.()).catch(e=>console.warn('[omx] Postinstall skipped after a n...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "const fs=require('fs');const p='./dist/scripts/postinstall.js';if(fs.existsSync(p))import(p).then(m=>m.main?.()).catch(e=>console.warn('[omx] Postinstall skipped after a n...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgdist/autoresearch/runtime.jsView file
1import { execFileSync, spawnSync } from 'child_process';
L2: import { existsSync } from 'fs';
High
Findings
2 Critical6 High6 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalPrevious Version Dangerous Deltadist/scripts/smoke-packed-install.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/autoresearch/runtime.js
HighShelldist/autoresearch/runtime.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/cli/setup.js
HighRuntime Package Installdist/mcp/code-intel-server.js
HighSemantic Analysis Limiteddist/cli/api.js#virtual:normalized:round1
MediumDynamic Requiredist/runtime/bridge.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistence
Affected versions and remediation
This report applies to oh-my-codex@0.21.2.
See all versions of oh-my-codex for other recorded verdicts.
- Review the evidence and your use of oh-my-codex@0.21.2 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.