HealthchecksvsZed Attack Proxy (ZAP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Healthchecks | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 73/100 | 80/100 |
| Rank in category | #2 of 12 in Uptime Monitoring | #4 of 78 in Security |
| GitHub stars | 10 464 | 16 059 |
| Stars, last 30 days | +106 | +244 |
| Stable releases, 12 months | 12 | 31 |
| Latest release | v5.0.3 · 27 Oct 2026 | w2026-10-23 · 23 Oct 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | BSD-3-Clause | Apache-2.0 |
| Main language | Python | Java |
Which one should you pick?
Zed Attack Proxy (ZAP) scores 80/100 against 73/100 for Healthchecks, so it is the safer default.
Zed Attack Proxy (ZAP) ships more often: 31 stable releases in the past year, against 12 for Healthchecks.
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; Healthchecks needs more configuration.
Zed Attack Proxy (ZAP) is growing faster right now (+244 stars in 30 days).
Healthchecks details →Zed Attack Proxy (ZAP) details →
Swap a project
Keep Healthchecks, compare it with
Keep Zed Attack Proxy (ZAP), compare it with