head to head · open source
codex-security vs code-on-incus
codex-security has 11,287 GitHub stars, 903 forks, 220 open issues and last shipped yesterday. code-on-incus has 771 stars, 67 forks, 24 open issues and last shipped yesterday. codex-security leads on adoption by 1,364% (11,287 vs 771 stars). codex-security is written in TypeScript under Apache-2.0; code-on-incus is written in Go under MIT. codex-security has attracted 8% as many forks as stars, code-on-incus 9%. 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 (codex), 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 | code-on-incus | |
|---|---|---|
| GitHub stars | ★ 11K | ★ 771 |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 903 | ⑂ 67 |
| 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 code-on-incus if
- You want the code-on-incus feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and code-on-incus 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 code-on-incus
code on incus ( coi ) Give every AI coding agent its own machine with active defense. coi runs your AI coding tool (Claude Code, Codex, opencode, pi, omp) inside its own isolated Linux system a full OS container with root access, systemd, Docker, and the freedom to install anything. The agent works like it would on a real server but it can't touch your host, can't see your credentials, and if it does something dangerous, coi pauses or kills the container on its own. One command drops you into a coding session. Your project is mounted, file permissions just work, and your SSH keys, tokens, and environment…
read the full code-on-incus 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 code-on-incus more popular?
codex-security has 11,287 GitHub stars and code-on-incus has 771. codex-security has the larger community by that measure.
Are codex-security and code-on-incus free?
Both are open source. codex-security is licensed under Apache-2.0 and code-on-incus under MIT. Neither carries a licence fee.
What is the difference between codex-security and code-on-incus?
codex-security is written in TypeScript and code-on-incus in Go. 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 code-on-incus?
Choose codex-security if you want the larger community (11,287 stars) or its Apache-2.0 licence terms. Choose code-on-incus if its feature set, stack or MIT licence fits better. Both are self-hostable.