head to head · open source
iFixAi vs open-kritt
iFixAi has 43,018 GitHub stars, 1,780 forks, 2 open issues and last shipped yesterday. open-kritt has 2,406 stars, 407 forks, 7 open issues and last shipped yesterday. iFixAi leads on adoption by 1,688% (43,018 vs 2,406 stars). iFixAi is written in Python under Apache-2.0; open-kritt is written in JavaScript under AGPL-3.0. iFixAi has attracted 4% as many forks as stars, open-kritt 17%. iFixAi was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (ai), 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
| iFixAi | open-kritt | |
|---|---|---|
| GitHub stars | ★ 43K | ★ 2.4K |
| License | Apache-2.0 | AGPL-3.0 |
| Written in | Python | JavaScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 1.8K | ⑂ 407 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick iFixAi if
- You weight community size — 43K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick open-kritt if
- You want the open-kritt feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches JavaScript
- You evaluated both and open-kritt fits your workflow better
About iFixAi
iFixAi English · 简体中文 · 日本語 · 한국어 Independent Auditing of AI Agents Catch your agent's mistakes and blind spots before the shit hits the fan. Quick start • Three ways to run • Test your agent • Scoring • Docs • Contributing One ifixai run , end to end: guided setup picks the system, judge, and suite; the run verifies the connection and saves your config; 32 inspections execute across five pillars; and the result lands as an A–F grade with a scored core pillar scorecard. What it is The existing Eval, Red teaming, and Observability Tools are evaluating the agent mainly based on tech capability (token efficiency…
read the full iFixAi overview →
About open-kritt
open·kritt Orchestrate AI agents to find real vulnerabilities in code. An open source, self hosted security and vulnerability research platform that turns focused AI analysis into de duplicated, ranked findings with configurable validation and enrichment. Website · Documentation · Getting started · Contributing · Owners · Research paper What is open·kritt? Pointing a model at an entire repository and asking it to find vulnerabilities rarely works well. open·kritt takes a focused approach: break the research into small, well defined tasks, run them across AI agents in parallel, and combine their output into…
read the full open-kritt 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 iFixAi or open-kritt more popular?
iFixAi has 43,018 GitHub stars and open-kritt has 2,406. iFixAi has the larger community by that measure.
Are iFixAi and open-kritt free?
Both are open source. iFixAi is licensed under Apache-2.0 and open-kritt under AGPL-3.0. Neither carries a licence fee.
What is the difference between iFixAi and open-kritt?
iFixAi is written in Python and open-kritt in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, iFixAi or open-kritt?
Choose iFixAi if you want the larger community (43,018 stars) or its Apache-2.0 licence terms. Choose open-kritt if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.