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.

Healthy · 81
81/100
Healthy

Actively maintained with regular releases.

Maintenance 32/40
Releases 25/25
Community 12/20
Momentum 12/15

Commit activity more than 80% of tracked projects; popularity more than 59%. How this is calculated.

Commits, last 11 months

2025-10: 98 commits 2025-11: 86 commits 2025-12: 99 commits 2026-01: 92 commits 2026-02: 48 commits 2026-03: 136 commits 2026-04: 110 commits 2026-05: 73 commits 2026-06: 98 commits 2026-07: 88 commits 2026-08: 122 commits
2025-10 1050 total 2026-08
Stars3.2k
Latest releasev2.14.0 · 21 Sept 2026
Repo updated25 Sept 2026
LicenceApache-2.0
Built withDocker, K8S, Ruby

Is Password Pusher actively maintained?

Over the last 11 months the project absorbed 1050 commits, of which 308 arrived in the most recent quarter — roughly 103 commits a month.

The most recent tagged release, v2.14.0, shipped within the last month — a current, installable version exists today.

Of the 25 projects we track in Pastebins, Password Pusher ranks #4 by health score — in the top quarter of its category.

What Password Pusher actually does

Password Pusher is a self-hosted utility designed for securely sharing sensitive text and credentials over the web. Items shared via the platform are configured to self-destruct automatically after a designated number of views or a specific timeframe elapses. It belongs to the pastebin category of applications, specifically focused on confidential data transmission.

Best fit: It is well-suited for teams or individuals who need a straightforward, ephemeral method for sending credentials or private notes to clients or colleagues without relying on third-party cloud services.

Worth knowing: The primary operational constraint is ensuring that the deletion mechanisms function correctly and that no unintended caching occurs in your infrastructure. It also faces significant overlap with built-in secret sharing features in established password managers.

Deployment notes

Given its containerised runtime stack using Docker and Kubernetes, you will typically need to configure a persistent volume for data storage, a reverse proxy to handle TLS termination, and a database backend depending on the underlying configuration.


Alternatives to Password Pusher

Projects in the same categories, ordered by health score.