Mobile-Security-Framework-MobSFvsZed Attack Proxy (ZAP)
Two self-hosted Security projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Mobile-Security-Framework-MobSF | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 78/100 | 80/100 |
| Rank in category | #8 of 78 in Security | #3 of 78 in Security |
| GitHub stars | 22 236 | 16 204 |
| Stars, last 30 days | +308 | +279 |
| Stable releases, 12 months | 8 | 34 |
| Latest release | v4.6.6 · 15 Nov 2026 | w2026-11-11 · 11 Nov 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | Apache-2.0 |
| Main language | Python | Java |
Which one should you pick?
Zed Attack Proxy (ZAP) scores 80/100 against 78/100 for Mobile-Security-Framework-MobSF, so it is the safer default.
Zed Attack Proxy (ZAP) ships more often: 34 stable releases in the past year, against 8 for Mobile-Security-Framework-MobSF.
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; Mobile-Security-Framework-MobSF needs more configuration.
Key differences
- License: Mobile-Security-Framework-MobSF is GPL-3.0, Zed Attack Proxy (ZAP) is Apache-2.0.
- Language: Mobile-Security-Framework-MobSF is written mainly in Python, Zed Attack Proxy (ZAP) in Java.
Mobile-Security-Framework-MobSF details →Zed Attack Proxy (ZAP) details →All Security projects →
Swap a project
Keep Mobile-Security-Framework-MobSF, compare it with
Keep Zed Attack Proxy (ZAP), compare it with