Check whether a Codex CLI npm release is actually ready before you install or upgrade it.
cnc verifies the main @openai/codex package and the platform builds you care
about. It checks both npm metadata and the real tarball URLs, using your
configured npm registry plus the official npm registry.
npm install -g codex-npm-check
cncOn first run, cnc asks which platforms to check and how many latest stable
Codex versions to inspect.
cnc
cnc 0.124.0
cnc --platform linux-x64,darwin-arm64 --latest 3
cnc 0.124.0 --platform win32-x64 --json
cnc --set
cnc --show
cnc --resetcncchecks the latest stable releases with your saved config.cnc 0.124.0checks one specific Codex version.--platformoverrides platforms for one run.--latestoverrides how many latest stable versions to check.--jsonprints machine-readable output.--set,--show, and--resetmanage saved config.
Checking latest 3 stable releases...
0.124.0: issues found ❌
main package: OK ✅
linux-x64: issues found ❌
configured: OK ✅
official: tarball unavailable ❌
darwin-arm64: OK ✅
0.123.0: OK ✅
main package: OK ✅
linux-x64: OK ✅
darwin-arm64: OK ✅
If any selected package is missing metadata or has an unavailable tarball in any
checked registry, cnc exits non-zero.
cnc catches npm publishing and registry problems, including:
- Missing
@openai/codexrelease metadata. - Missing platform build metadata, such as
@openai/codex@0.124.0-win32-x64. - Tarball URLs that exist in metadata but return an error.
- Mirror registry drift from the official npm registry.
It does not run Codex after install, so it will not catch runtime bugs, macOS signing problems, config regressions, or local npm optional dependency bugs when the packages and tarballs are already available.
linux-x64linux-arm64darwin-x64darwin-arm64win32-x64win32-arm64
Config is stored at:
~/.config/codex-npm-check/config.json$XDG_CONFIG_HOME/codex-npm-check/config.json
Tests and scripts can override the config base directory with CNC_CONFIG_HOME.
git clone https://github.com/FelixWardUS/codex-npm-check.git
cd codex-npm-check
npm test
npm install -g .Requires Node.js 20+ and npm in PATH.