mantis vs shippie
shippie is much bigger: 2.5k stars against 935. Over the days we have tracked them mantis moved +10288.9% and shippie +5.3%, so mantis is growing faster right now.
mantis leads on 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
A modular, stack-agnostic suite of security review skills that lets coding agents find, reproduce, dedupe, and patch vulnerabilities with sandboxed execution and a sequential pipeline.
- Stars
- 935
- Tracked growth
- +10288.9%
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Your API key; model/compute costs apply.
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.3%
- Maturity
- ●●●●●
- Last commit
- 1d 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 | mantis | 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. | ●●●●● Dedupe & filters | ●●●●● Configurable filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Customizable prompts | ●●●●● Rules & prompts |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● API-key cloud |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own-key | ●●●●● Multiple providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Agent + API key | ●●●●● Quick start |
Which one to pick
Pick mantis if…
Security-first — pick Mantis when you need a focused, extensible toolkit of agent skills specialized for end-to-end vulnerability discovery, reproduction, and patching in isolated environments.
- Model freedom: Bring-your-own-key (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
google/mantis
mattzcarey/shippie
Questions people ask
Is mantis better than shippie?
mantis leads on model freedom. shippie does not take any axis by a clear margin. mantis is worth picking when security-first — pick Mantis when you need a focused, extensible toolkit of agent skills specialized for end-to-end vulnerability discovery, reproduction, and patching in isolated environments.
Which of mantis and shippie keeps my code private?
mantis: Self-hostable (4/5). shippie: API-key cloud (3/5).
What does each one cost to run?
mantis: Your API key; model/compute costs apply.. shippie: Your API key, per-PR.
Full profiles: google/mantis and mattzcarey/shippie. Everything else in Code review agents.