temporalvsZed Attack Proxy (ZAP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| temporal | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 83/100 | 80/100 |
| Rank in category | #1 of 1 in Workflow | #4 of 78 in Security |
| GitHub stars | 24 047 | 16 062 |
| Stars, last 30 days | +787 | +247 |
| Stable releases, 12 months | 11 | 31 |
| Latest release | v1.30.8 · 12 Oct 2026 | w2026-10-23 · 23 Oct 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Go | Java |
Which one should you pick?
temporal scores 83/100 against 80/100 for Zed Attack Proxy (ZAP), so it is the safer default.
Zed Attack Proxy (ZAP) ships more often: 31 stable releases in the past year, against 11 for temporal.
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; temporal needs more configuration.
temporal is growing faster right now (+787 stars in 30 days).
temporal details →Zed Attack Proxy (ZAP) details →
Swap a project
Keep temporal, compare it with
Keep Zed Attack Proxy (ZAP), compare it with