codex-security
OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security
Runssource: GitHubhomepageTypeScriptApache-2.0commit 8c78e6553215
TypeScript, Apache-2.0 licensed. The project labels itself: ai security, application security, cli, code scanning, codex, codex security, cybersecurity and devsecops.
codex-security runs. An Argusic agent installed it in 6 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.
TypeScript SDK builds and lints cleanly, CLI prints version 0.1.31 and full help, bun test suite passes 551+ tests, Python pytest suite passes 615+ tests, ruff lint/format pass, bundled plugin builds with 142 files, and pre-submit compatibility checks all pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 94.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 is too old (requires >=22.13.0)2 minutes
- pnpm not available and corepack signature verification failed for [email protected]1 minute
- Stale /work/repo/.npmrc with prefix=/home/runner/.npm-global prevented npm configuration changes0.5 minutes
- Python pip install failed due to externally-managed environment0.5 minutes
- Native prebuilt directory plugins/codex-security/native/prebuilt/ did not exist0.5 minutes
- bwrap: No permissions to create a new namespace (kernel restriction)0.5 minutes
- Install time
- 6 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 6 hit, 5 fixed with no human help
- How the result was proved
- bun test over 25 files exited 0 with 551 pass/7 skip/0 fail; python -m pytest over all plugin tests exited 0 with 615 pass/1 fail (Windows-only, expected)/4 skip; node bin/codex-security.mjs --version returned 0.1.31; --help returned help text with 20+ commands
- Model tokens used
- 79,006
- Exact commit tested
- 8c78e6553215
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
4. **Python externally-managed environment** — created a venv and installed plugin+test deps there 5. **Native prebuilt directory missing** — created stub files for all platforms so bundled plugin b… 6. **bwrap (bubblewrap) namespace restriction** in this container — some Argusic Agent config tests… **Verified:** - `bun test` over 25 test files: **551 pass, 7 skip, 0 fail** - `python -m pytest` over all Python plugin tests: **615 pass, 1 fail (Windows E2E, expected on Lin… - `codex-security --version` returns `0.1.31` - `codex-security --help` shows 20+ commands - `ruff check` and `ruff format --check` both pass - TypeScript `tsc --noEmit` and `tsc -p tsconfig.ci.json` both succeed - `check_plugin_source_compatibility.mjs` passes - Bundled plugin builds with 142 files
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 6 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 6 errors during setup, 1 of which were not solved.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 96.67 | 0.18 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.26 |
Topics (from GitHub)
ai-securityapplication-securityclicode-scanningcodexcodex-securitycybersecuritydevsecopsnodejsnpmopenaisdksecuritytypescriptvulnerability-scanning
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/codex-security)Questions
- Does codex-security run?
- Yes. codex-security runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test codex-security?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8c78e6553215. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test codex-security?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does codex-security take to install?
- 6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does codex-security need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing codex-security?
- 6 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for codex-security?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.