head to head · open source
code-review-graph vs DeepAudit
code-review-graph has 32,563 GitHub stars, 2,964 forks, 163 open issues and last shipped 5 days ago. DeepAudit has 7,250 stars, 875 forks, 94 open issues and last shipped 2 days ago. code-review-graph leads on adoption by 349% (32,563 vs 7,250 stars). code-review-graph is written in Python under MIT; DeepAudit is written in Python under AGPL-3.0. code-review-graph has attracted 9% as many forks as stars, DeepAudit 12%. DeepAudit was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (code-review, llm), 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
| code-review-graph | DeepAudit | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 7.3K |
| License | MIT | AGPL-3.0 |
| Written in | Python | Python |
| Last push | 2026-10-29 | 2026-11-01 |
| Forks | ⑂ 3.0K | ⑂ 875 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick code-review-graph if
- You weight community size — 33K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick DeepAudit if
- You want the DeepAudit feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Python
- You evaluated both and DeepAudit fits your workflow better
About code-review-graph
code review graph Stop burning tokens. Start reviewing smarter. English 简体中文 日本語 한국어 हिन्दी Usage · Commands · FAQ · Troubleshooting · GitHub Action · Reproducing the benchmarks · Roadmap AI coding tools can end up re reading large parts of your codebase on review tasks. code review graph fixes that. It builds a structural map of your code with Tree sitter, tracks changes incrementally, and gives your AI assistant precise context via MCP so it reads only what matters. Quick Start One command sets up everything. install detects which AI coding tools you have, writes the correct MCP configuration for each one…
read the full code-review-graph overview →
About DeepAudit
DeepAudit 人人拥有的 AI 审计战队，让漏洞挖掘触手可及 🦸♂️ 简体中文 English 📸 界面预览 🤖 Agent 审计入口 首页快速进入 Multi Agent 深度审计 📋 审计流日志 实时查看 Agent 思考与执行过程 🎛️ 智能仪表盘 一眼掌握项目安全态势 ⚡ 即时分析 粘贴代码 / 上传文件，秒出结果 🗂️ 项目管理 GitHub/GitLab/Gitea 导入，多项目协同管理 📊 专业报告 一键导出 PDF / Markdown / JSON （图中为快速模式，非Agent模式报告） 🏆 CVE 漏洞发现 DeepAudit（闭源版本） 已成功发现并获得 49 个 CVE 编号 和 6 个 GHSA 安全公告🦞 涉及17个知名开源项目 OpenClaw🦞 漏洞挖掘成果 DeepAudit 内测版本对 OpenClaw 项目进行了深度安全审计，目前已发现 6 个安全漏洞 ，均已被官方确认并发布安全公告（GHSA）。漏洞类型覆盖命令注入、签名验证绕过、远程代码执行、凭证泄露、资源耗尽及敏感信息泄露，其中包含多个 High 级别漏洞。更多漏洞仍在持续挖掘中。 [CVE 2025 58045](
read the full DeepAudit overview →
More in Developer Tools
Related comparisons
More Version Control & Collaboration projects
Compare either of these against the rest of the Version Control & Collaboration field.
Frequently asked questions
Is code-review-graph or DeepAudit more popular?
code-review-graph has 32,563 GitHub stars and DeepAudit has 7,250. code-review-graph has the larger community by that measure.
Are code-review-graph and DeepAudit free?
Both are open source. code-review-graph is licensed under MIT and DeepAudit under AGPL-3.0. Neither carries a licence fee.
What is the difference between code-review-graph and DeepAudit?
code-review-graph is written in Python and DeepAudit in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, code-review-graph or DeepAudit?
Choose code-review-graph if you want the larger community (32,563 stars) or its MIT licence terms. Choose DeepAudit if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.