head to head · open source
codex-security vs nono
codex-security has 11,287 GitHub stars, 903 forks, 220 open issues and last shipped yesterday. nono has 4,806 stars, 326 forks, 201 open issues and last shipped yesterday. codex-security leads on adoption by 135% (11,287 vs 4,806 stars). codex-security is written in TypeScript under Apache-2.0; nono is written in Rust under Apache-2.0. codex-security has attracted 8% as many forks as stars, nono 7%. codex-security was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (ai-security), 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 | nono | |
|---|---|---|
| GitHub stars | ★ 11K | ★ 4.8K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | TypeScript | Rust |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 903 | ⑂ 326 |
| 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 nono if
- You want the nono feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Rust
- You evaluated both and nono 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 nono
Built by the team that brought you Sigstore The standard for secure software attestation, used by PyPI, npm, brew, and Maven Central [!NOTE] In the lead up to a 1.0 release, APIs are stabilizing. API changes may still occur where necessary, but will be kept to a minimum. [!IMPORTANT] Organization migration: The official nono registry namespace has moved from always further to nolabs ai . Update any references in your scripts, profiles, and CI. If you already have a pack installed under the old namespace, remove it first before pulling from the new one: The old namespace will be retired — migrate now. Run AI…
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 nono more popular?
codex-security has 11,287 GitHub stars and nono has 4,806. codex-security has the larger community by that measure.
Are codex-security and nono free?
Both are open source. codex-security is licensed under Apache-2.0 and nono under Apache-2.0. Neither carries a licence fee.
What is the difference between codex-security and nono?
codex-security is written in TypeScript and nono in Rust. 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 nono?
Choose codex-security if you want the larger community (11,287 stars) or its Apache-2.0 licence terms. Choose nono if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.