RemoteTerm for MeshCorevsZed Attack Proxy (ZAP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| RemoteTerm for MeshCore | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 45/100 | 80/100 |
| Rank in category | #4 of 4 in Amateur Radio | #4 of 78 in Security |
| GitHub stars | 337 | 16 063 |
| Stars, last 30 days | +0 | +240 |
| Stable releases, 12 months | 10 | 31 |
| Latest release | 3.17.1 · 26 Jul 2026 | w2026-10-23 · 23 Oct 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Python | Java |
Which one should you pick?
Zed Attack Proxy (ZAP) scores 80/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.
Zed Attack Proxy (ZAP) ships more often: 31 stable releases in the past year, against 10 for RemoteTerm for MeshCore.
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; RemoteTerm for MeshCore needs more configuration.
Zed Attack Proxy (ZAP) is growing faster right now (+240 stars in 30 days).
RemoteTerm for MeshCore details →Zed Attack Proxy (ZAP) details →