selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

ThreatMappervsZed Attack Proxy (ZAP)

Two self-hosted Security projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

ThreatMapperZed Attack Proxy (ZAP)
Score65/10080/100
Rank in category#21 of 78 in Security#3 of 78 in Security
GitHub stars5 33116 201
Stars, last 30 days+7+276
Stable releases, 12 months134
Latest releasev2.5.8 · 7 Mar 2026w2026-11-11 · 11 Nov 2026
SetupAdvancedEasy
Official Docker imageYesYes
LicenseApache-2.0Apache-2.0
Main languageTypescriptJava

Which one should you pick?

Zed Attack Proxy (ZAP) scores 80/100 against 65/100 for ThreatMapper, so it is the safer default.

Zed Attack Proxy (ZAP) ships more often: 34 stable releases in the past year, against 1 for ThreatMapper.

If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; ThreatMapper needs more configuration.

Zed Attack Proxy (ZAP) is growing faster right now (+276 stars in 30 days).

Key differences

  • Language: ThreatMapper is written mainly in Typescript, Zed Attack Proxy (ZAP) in Java.
  • Platforms only ThreatMapper lists: Helm.
  • Platforms only Zed Attack Proxy (ZAP) lists: Docker, Flatpak, Homebrew, Linux and 4 more.
  • Features only ThreatMapper lists: Agent-based sensor coverage of multiple platforms, Agentless cloud configuration scanning, Air-gapped deployment support, API access with console API key and 11 more.
  • Features only Zed Attack Proxy (ZAP) lists: Active scanning, Add-on marketplace / plugin architecture, API scanning, Authenticated scans and 10 more.

Swap a project

Keep ThreatMapper, compare it with
Keep Zed Attack Proxy (ZAP), compare it with