Password Pusher vs Yopass
Both are self-hosted pastebins projects. This page compares how well each one is actually maintained — the part you cannot see from a feature list.
| Password Pusher | Yopass | |
|---|---|---|
| Health score | 81/100 | 83/100 |
| Commits (11 mo) | 1050 | 988 |
| Commits (last 3 mo) | 308 | 452 |
| Stars | 3.2k | 3.2k |
| Latest release | 21 Sept 2026 | 18 Sept 2026 |
| Licence | Apache-2.0 | Apache-2.0 |
| Built with | Docker, K8S, Ruby | Go, Docker |
| Typical RAM | 1 GB | 1 GB |
Password Pusher
Dead-simple application to securely communicate passwords (or text) over the web. Passwords automatically expire after a certain number of views and/or time has passed.
Actively maintained with regular releases.
Commit activity more than 80% of tracked projects; popularity more than 59%. How this is calculated.
Commits, last 11 months
Yopass
Secure sharing of secrets, passwords and files.
High commit volume, frequent releases and growing activity.
Commit activity more than 79% of tracked projects; popularity more than 59%. 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 pastebins.