imgproxy 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.

imgproxy scores 75 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.

	imgproxy	Tinyproxy
Health score	75/100	38/100
Commits (11 mo)	238	19
Commits (last 3 mo)	119	5
Stars	11k	6k
Latest release	14 Sept 2026	7 Mar 2026
Licence	MIT	GPL-2.0
Built with	Go, Docker, K8S	C, deb
Typical RAM	1 GB	1 GB

imgproxy

Fast and secure standalone server for resizing and converting remote images.

75/100

Healthy

Actively maintained with regular releases.

Maintenance 19/40

Releases 25/25

Community 16/20

Momentum 15/15

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