Deadend CLIvsZed Attack Proxy (ZAP)
Two self-hosted Security projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Deadend CLI | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 48/100 | 80/100 |
| Rank in category | #49 of 78 in Security | #3 of 78 in Security |
| GitHub stars | 331 | 16 201 |
| Stars, last 30 days | +12 | +276 |
| Stable releases, 12 months | 6 | 34 |
| Latest release | v0.1.15 · 11 Apr 2026 | w2026-11-11 · 11 Nov 2026 |
| Setup | Moderate | Easy |
| Official Docker image | No | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Python | Java |
Which one should you pick?
Zed Attack Proxy (ZAP) scores 80/100 against 48/100 for Deadend CLI, so it is the safer default.
Zed Attack Proxy (ZAP) ships more often: 34 stable releases in the past year, against 6 for Deadend CLI.
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; Deadend CLI needs more configuration.
Zed Attack Proxy (ZAP) is growing faster right now (+276 stars in 30 days).
Key differences
- License: Deadend CLI is AGPL-3.0, Zed Attack Proxy (ZAP) is Apache-2.0.
- Language: Deadend CLI is written mainly in Python, Zed Attack Proxy (ZAP) in Java.
- Only Zed Attack Proxy (ZAP) ships an official Docker image.
- Platforms only Zed Attack Proxy (ZAP) lists: Docker, Flatpak, Homebrew, Scoop and 2 more.
- Features only Deadend CLI lists: Autonomous penetration testing, Confidence-based decision making, Custom sandboxed tools, Embedding Model Support and 6 more.
- Features only Zed Attack Proxy (ZAP) lists: Active scanning, Add-on marketplace / plugin architecture, API scanning, Authenticated scans and 10 more.
Deadend CLI details →Zed Attack Proxy (ZAP) details →All Security projects →
Swap a project
Keep Deadend CLI, compare it with
Keep Zed Attack Proxy (ZAP), compare it with