open-kritt vs shippie
The two are close in size: 2.1k stars for open-kritt, 2.5k for shippie. Over the days we have tracked them open-kritt moved +25.7% and shippie +5.4%, so open-kritt is growing faster right now.
open-kritt leads on noise control and model freedom. shippie does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Orchestrates focused AI agent workflows in disposable job containers to find, validate and de-duplicate real vulnerabilities with PoC generation and ranking.
- Stars
- 2.1k
- Tracked growth
- +25.7%
- Maturity
- ●●●●●
- Last commit
- 15h ago
- Language
- JavaScript
- License
- AGPL-3.0
- Cost to run
- Requires model API key (your provider's billing applies).
Provides an extendable agent loop built on flue/pi with Model Context Protocol (MCP) support to explore the repo using real developer tools and integrate external tools.
- Stars
- 2.5k
- Tracked growth
- +5.4%
- Maturity
- ●●●●●
- Last commit
- 5d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Your API key, per-PR
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | open-kritt | shippie |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Repo exploration |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Deduplication & ranking | ●●●●● Configurable filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Workflow & rules | ●●●●● Rules & prompts |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hosted (cloud models) | ●●●●● API-key cloud |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-key (multiple) | ●●●●● Multiple providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Docker + CLI setup | ●●●●● Quick start |
Which one to pick
Pick open-kritt if…
Self-hosted — run customizable, security-focused AI research workflows locally with built-in validation, de-duplication and BYO model access.
- Noise control: Deduplication & ranking (5/5 against 3/5)
- Model freedom: Bring-your-key (multiple) (5/5 against 3/5)
Pick shippie if…
Extensible — pick Shippie when you want a provider-agnostic, extendable code-review workflow that can run locally or in CI and integrate external tools via MCP.
What people want from each one
Kritt-ai/open-kritt
mattzcarey/shippie
Questions people ask
Is open-kritt better than shippie?
open-kritt leads on noise control and model freedom. shippie does not take any axis by a clear margin. open-kritt is worth picking when self-hosted — run customizable, security-focused AI research workflows locally with built-in validation, de-duplication and BYO model access.
Which of open-kritt and shippie keeps my code private?
open-kritt: Self-hosted (cloud models) (4/5). shippie: API-key cloud (3/5).
What does each one cost to run?
open-kritt: Requires model API key (your provider's billing applies).. shippie: Your API key, per-PR.
Full profiles: Kritt-ai/open-kritt and mattzcarey/shippie. Everything else in Code review agents.