GitProxy vs imgproxy
Both are self-hosted proxy projects. This page compares how well each one is actually maintained — the part you cannot see from a feature list.
| GitProxy | imgproxy | |
|---|---|---|
| Health score | 69/100 | 75/100 |
| Commits (11 mo) | 525 | 238 |
| Commits (last 3 mo) | 391 | 119 |
| Stars | 253 | 11k |
| Latest release | 8 Sept 2026 | 14 Sept 2026 |
| Licence | Apache-2.0 | MIT |
| Built with | Nodejs, Docker | Go, Docker, K8S |
| Typical RAM | 1 GB | 1 GB |
GitProxy
Proxy for Git that applies rules and workflows to all outgoing git push operations and ensures they are compliant. It supports both HTTP/HTTPS and SSH protocols with security scanning and validation.
Actively maintained with regular releases.
Commit activity more than 65% of tracked projects; popularity more than 14%. How this is calculated.
Commits, last 11 months
imgproxy
Fast and secure standalone server for resizing and converting remote images.
Actively maintained with regular releases.
Commit activity more than 47% of tracked projects; popularity more than 80%. How this is calculated.
Commits, last 11 months
How to read this
Everything above is measured, not opinion: commit counts and release dates come from the public repositories, and the health score ranks each project against all 1352 projects we track. Read the full method.
What this comparison deliberately does not do is tell you which has the better feature set. Maintenance health tells you which project will still be receiving security fixes in two years. Decide that first, then compare features on the projects that survive the filter.
See every option in this category: self-hosted proxy.