GitProxy vs Tinyproxy

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 scores 69 against Tinyproxy's 38, putting it clearly ahead on the strength of a higher commit volume and more recent releases. That measures project health, not feature fit — Tinyproxy may still be the right choice if it does what you need.

	GitProxy	Tinyproxy
Health score	69/100	38/100
Commits (11 mo)	525	19
Commits (last 3 mo)	391	5
Stars	253	6k
Latest release	8 Sept 2026	7 Mar 2026
Licence	Apache-2.0	GPL-2.0
Built with	Nodejs, Docker	C, deb
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.

69/100

Healthy

Actively maintained with regular releases.

Maintenance 26/40

Releases 25/25

Community 3/20

Momentum 15/15

Commit activity more than 65% of tracked projects; popularity more than 14%. How this is calculated.

Commits, last 11 months

Tinyproxy

Light-weight HTTP/HTTPS proxy daemon.

38/100

Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 4/40

Releases 16/25

Community 14/20

Momentum 4/15

Commit activity more than 10% of tracked projects; popularity more than 70%. 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.