head to head · open source
iFixAi vs ship-safe
iFixAi has 43,018 GitHub stars, 1,780 forks, 2 open issues and last shipped yesterday. ship-safe has 870 stars, 115 forks, 9 open issues and last shipped 17 days ago. iFixAi leads on adoption by 4,845% (43,018 vs 870 stars). iFixAi is written in Python under Apache-2.0; ship-safe is written in JavaScript under MIT. iFixAi has attracted 4% as many forks as stars, ship-safe 13%. iFixAi was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (cli), 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 | ship-safe | |
|---|---|---|
| GitHub stars | ★ 43K | ★ 870 |
| License | Apache-2.0 | MIT |
| Written in | Python | JavaScript |
| Last push | 2026-11-02 | 2026-10-17 |
| Forks | ⑂ 1.8K | ⑂ 115 |
| 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 ship-safe if
- You want the ship-safe feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and ship-safe 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 ship-safe
The independent security agent for AI written software. It finds issues, investigates whether they are real, and shows you the evidence. Website · Docs · Security & Data Flow · Benchmark · Pricing · Blog · Contribute Ship Safe CLI Ship Safe runs locally in your repo and works in two layers. A deterministic engine finds issues across application code, AI agents, MCP configs, prompts, dependencies, CI/CD, secrets, and cloud adjacent configuration. Fast, repeatable, and benchmarked — this is the sensor layer. An investigation layer then decides what the findings are worth. It traces the value that reaches a sink…
read the full ship-safe 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 ship-safe more popular?
iFixAi has 43,018 GitHub stars and ship-safe has 870. iFixAi has the larger community by that measure.
Are iFixAi and ship-safe free?
Both are open source. iFixAi is licensed under Apache-2.0 and ship-safe under MIT. Neither carries a licence fee.
What is the difference between iFixAi and ship-safe?
iFixAi is written in Python and ship-safe 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 ship-safe?
Choose iFixAi if you want the larger community (43,018 stars) or its Apache-2.0 licence terms. Choose ship-safe if its feature set, stack or MIT licence fits better. Both are self-hostable.