head to head · open source
codex-security vs CyberStrike
codex-security has 11,287 GitHub stars, 903 forks, 220 open issues and last shipped yesterday. CyberStrike has 3,354 stars, 574 forks, 43 open issues and last shipped yesterday. codex-security leads on adoption by 237% (11,287 vs 3,354 stars). codex-security is written in TypeScript under Apache-2.0; CyberStrike is written in TypeScript under AGPL-3.0. codex-security has attracted 8% as many forks as stars, CyberStrike 17%. codex-security was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (ai-security, cybersecurity), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| codex-security | CyberStrike | |
|---|---|---|
| GitHub stars | ★ 11K | ★ 3.4K |
| License | Apache-2.0 | AGPL-3.0 |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 903 | ⑂ 574 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick codex-security if
- You weight community size — 11K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick CyberStrike if
- You want the CyberStrike feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and CyberStrike fits your workflow better
About codex-security
Codex Security @openai/codex security is a CLI and TypeScript SDK for defining security policy and finding, validating, and fixing security vulnerabilities in your code. 👉👉 See the Codex Security documentation for full documentation. Some cybersecurity requests and protected findings require approval through Trusted Access for Cyber. To join the program, visit chatgpt.com/cyber. Quick start Requires Node.js 22.13.0 or later and Python 3.10 or later. For CI, set OPENAI API KEY instead of signing in. Generate SECURITY.md Draft repository wide or component scoped SECURITY.md guidance for future scans: The command…
read the full codex-security overview →
About CyberStrike
English 简体中文 繁體中文 한국어 Deutsch Español Français Italiano Dansk 日本語 Polski Русский Bosanski العربية Norsk Português (Brasil) ไทย Türkçe Українська বাংলা Ελληνικά Tiếng Việt हिन्दी The first open source AI agent built for offensive security. Automated penetration testing from your terminal — plug in your Claude, GPT, or any LLM subscription and turn it into an autonomous red team agent with 13+ specialized agents, 7,600+ security skills, and 120+ OWASP test cases. 150+ AI providers • 5,300+ models • 56+ built in tools • 176+ MCP tools Quick Start • Intelligence Layer • What Makes It…
read the full CyberStrike overview →
More in AI & Machine Learning
Related comparisons
More AI Security & Privacy projects
Compare either of these against the rest of the AI Security & Privacy field.
Frequently asked questions
Is codex-security or CyberStrike more popular?
codex-security has 11,287 GitHub stars and CyberStrike has 3,354. codex-security has the larger community by that measure.
Are codex-security and CyberStrike free?
Both are open source. codex-security is licensed under Apache-2.0 and CyberStrike under AGPL-3.0. Neither carries a licence fee.
What is the difference between codex-security and CyberStrike?
codex-security is written in TypeScript and CyberStrike in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, codex-security or CyberStrike?
Choose codex-security if you want the larger community (11,287 stars) or its Apache-2.0 licence terms. Choose CyberStrike if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.