Bitwarden client apps (web, browser extension, desktop, and cli).
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 68%
bitwarden/clients has a recorded first-timer success rate of 68.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bitwarden/clients respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 66.8 places bitwarden/clients in the A tier.
The external contributor pull request merge rate for bitwarden/clients is 66.6%, based on public PR activity from non-core contributors.
bitwarden/clients currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Bitwarden client apps (web, browser extension, desktop, and cli).
Balanced & professional review environment in bitwarden/clients. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/bitwarden/clients?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
Steps To Reproduce Navigate to any saved item containing a custom hidden field. Click on the 'Reveal Data' icon. The number of masked symbols corresponds to the exact number of characters in the hidden field data. While passwords in the web application no longer reveal character length, hidden custom fields do, resulting in inconsistency and potential security vulnerabilities. Expected Result The masked hidden field data appear to be the same length, regardless of the actual number of characters contained within the field. Actual Result The length of the masked symbols matches the actual hidden data, unintentionally revealing the true length of the concealed information. Screenshots or Videos No response Additional Context No response Operating System Windows Operating System Version Windows 11 Pro 25H2 Web Browser Microsoft Edge Browser Version 152.0.4191.62 Build Version 2026.8.1 Issue Tracking Info I understand that work is tracked outside of Github. A PR will be linked to this
Steps To Reproduce MS Account with TOTP active log in to TOTP input try autofilling TOTP Expected Result Autofilling TOTP works. Actual Result It does not. Screenshots or Videos No response Additional Context This issue is a successor of #20304. Since the last fix (#20481), Microsoft has seemingly changed the content of aria-describedby. <input id="idTxtBx_SAOTCC_OTC" name="otc" class="form-control" type="tel" autocomplete="off" aria-required="true" data-bind="attr: { 'maxlength': otcLength, 'aria-labelledby': 'idDiv_SAOTCC_Title','aria-describedby': 'idDiv_SAOTCS_Title idDiv_SAOTCC_Description idSpan_SAOTCC_Error_OTC' }, css: { 'has-error': error }, textInput: otcInputTextbox.value, ariaLabel: str['CT_SAOTCC_STR_OTC_TBHint'], hasFocusEx: otcInputTextbox.focused, placeholder: $placeholderText" maxlength="6" aria-labelledby="idDiv_SAOTCC_Title" aria-describedby="idDiv_SAOTCS_Ti
Steps To Reproduce Prerequisites : 2FA must be enable with the related account In Firefox, set language to Deutsch or any other language than English Go to Web Vault (https://vault.bitwarden.eu) Fill in your credentials The Bitwarden browser extension doesn't show the TOTP code / "Fill verification code" if the page locale is not English (us, gb, ca) Expected Result Actual Result (page not in English) Screenshots or Videos No response Additional Context No response Operating System Windows Operating System Version No response Web Browser Firefox/Edge Browser Version 147 Build Version 2026.2.0 (web vault) 2025.12.1 (Firefox add-on) Issue Tracking Info I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to bitwarden/clients, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of bitwarden/clients acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.6% were successfully merged into the primary branch.
bitwarden/clients has a recorded first-timer success rate of 68.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 66.8 places bitwarden/clients in the Welcoming tier.
The external pull request merge rate is 66.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bitwarden/clients currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bitwarden/clients are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.