/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

dani-garcia/vaultwarden

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:54:49.750Z

3mo ago

dani-garcia/vaultwarden

Vaultwarden is a Rust-based, self-hosted Bitwarden-compatible server with strong Docker/container support. It is very active, widely forked, and appears aimed at people who want an alternative to Bitwarden's official server for self-hosting.

Loading tags...

Stars57,553

Forks2,667

Default branchmain

Last pushed2026-03-29T21:15:48Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if SSO/IdP integration is the deciding requirement. Choose upstream if you want the most current, general-purpose Vaultwarden with lower maintenance risk.

Prefer this fork only if you need its legacy Send/policy behavior or must stay on an old snapshot. For most adopters, current upstream Vaultwarden is the safer and lower-risk choice.

Choose this fork if your main need is Chinese localization of Vaultwarden’s admin and template experience. Choose upstream instead if you want the latest server behavior, broad compatibility, and the least divergence risk.

Choose this fork only if you need its old, specific behavior and are willing to live without upstream progress. For most adopters, current Vaultwarden upstream is the safer choice.

Choose this fork if your main goal is Chinese-language usability on top of standard Vaultwarden. Choose upstream if you care more about receiving the latest fixes and operational changes quickly.

Prefer this fork if your main need is Simplified Chinese localization for Vaultwarden templates. Prefer upstream if you care about current features, fixes, and long-term maintenance.

Choose this fork only if the AWS/serverless deployment model is the main requirement. If you want the most current Vaultwarden feature set, fastest upstream fixes, or the simplest self-hosted install, upstream is the better default.

Choose this fork if Argon2-at-rest policy and deployment customization matter more than staying close to upstream. Avoid it if you want the safest upgrade path and the newest upstream fixes with minimal fork-specific maintenance.

Choose this fork if your priority is specialized compatibility or deployment constraints that upstream does not cover well. Choose upstream if you want the safest path for current fixes, broader testing, and easier long-term maintenance.

Prefer this fork only if Windows compilation is the primary requirement. If you want the latest Vaultwarden behavior and do not need Windows-specific packaging, upstream is the better default because this fork is narrowly scoped and already behind.

Fork comparison

Timshel/vaultwarden

70/100

active

significant_divergence

Choose this fork if SSO/IdP integration is the deciding requirement. Choose upstream if you want the most current, general-purpose Vaultwarden with lower maintenance risk.

Likely purpose

A Vaultwarden variant centered on adding OpenID Connect / SSO support and related enterprise identity workflows, likely for self-hosters who need integration with systems like Authentik, Keycloak, or Zitadel.

Best for

Self-hosters who need Bitwarden-compatible service with OpenID Connect or SSO.; Organizations already using Authentik, Keycloak, or Zitadel.; Operators willing to trade upstream freshness for identity-provider integration.; Teams managing multiple users and org memberships through external identity systems.

Additional features

OpenID Connect / SSO support and documentation (`SSO.md`).
Identity-provider integration work for Authentik, Keycloak, and Zitadel, including dockerized demo or init assets.
Organization sync workflows such as invite, membership, and group handling tied to SSO.
SSO role-mapping and login-path changes in auth and identity handling.
Playwright/test and CI adjustments to support the added auth flows.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

Fork is 154 commits behind upstream, so it likely lags newer Vaultwarden fixes and upstream enhancements.
Upstream changes to core compatibility, security, or admin workflows may not be present yet.
The extra SSO-focused surface can make the fork less plug-and-play for users who do not need an identity provider.
It trails upstream by 154 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want self-hosted Bitwarden compatibility plus centralized login through an external IdP.
Appears aimed at real deployment workflows rather than a proof-of-concept, with Docker and test coverage changes.
Recent activity suggests it is still being maintained.
Strong fit for orgs that want SSO-driven access and org synchronization.

Risks

Material divergence from upstream increases merge and maintenance risk.
Behind upstream means you may miss fixes unless you track them manually.
SSO additions can add configuration and operational complexity.
The large docker/authentik and identity changes suggest a narrower deployment focus than upstream.