Deadend CLIvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Deadend CLI | mitmproxy | |
|---|---|---|
| Score | 46/100 | 86/100 |
| Rank in category | #54 of 78 in Security | #1 of 48 in Network Monitoring |
| GitHub stars | 319 | 46 451 |
| Stars, last 30 days | — | +1 316 |
| Stable releases, 12 months | 6 | 5 |
| Latest release | v0.1.15 · 11 Apr 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | No | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Python | Python |
Which one should you pick?
mitmproxy scores 86/100 against 46/100 for Deadend CLI, so it is the safer default.
Deadend CLI ships more often: 6 stable releases in the past year, against 5 for mitmproxy.
mitmproxy is growing faster right now (+1 316 stars in 30 days).
Deadend CLI details →mitmproxy details →
Swap a project
Keep Deadend CLI, compare it with
Keep mitmproxy, compare it with