GitProxyvsOAuth2 Proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| GitProxy | OAuth2 Proxy | |
|---|---|---|
| Score | 53/100 | 75/100 |
| Rank in category | #39 of 78 in Security | #3 of 19 in Identity & Auth |
| GitHub stars | 268 | 15 381 |
| Stars, last 30 days | +6 | +223 |
| Stable releases, 12 months | 9 | 11 |
| Latest release | v2.3.1 · 16 Nov 2026 | v7.15.6 · 5 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Typescript | Go |
Which one should you pick?
OAuth2 Proxy scores 75/100 against 53/100 for GitProxy, so it is the safer default.
OAuth2 Proxy ships more often: 11 stable releases in the past year, against 9 for GitProxy.
OAuth2 Proxy is growing faster right now (+223 stars in 30 days).
Key differences
- License: GitProxy is Apache-2.0, OAuth2 Proxy is MIT.
- Language: GitProxy is written mainly in Typescript, OAuth2 Proxy in Go.
- Platforms only GitProxy lists: Build from Source, NPM.
- Platforms only OAuth2 Proxy lists: Go Install, Helm, Linux.
- Features only GitProxy lists: Attestation workflow, Audit Logging, Author email validation, Commit message validation and 10 more.
- Features only OAuth2 Proxy lists: Configuration validation, Custom Templates, Email and group access control, Health check endpoints and 9 more.
GitProxy details →OAuth2 Proxy details →
Swap a project
Keep GitProxy, compare it with
Keep OAuth2 Proxy, compare it with