HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bitwarden
clients
TypeScript2016–2026
bitwarden / clients

clients

Bitwarden client apps (web, browser extension, desktop, and cli).

56Distinct people
68Mentions
0Explicit recommenders
14.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Bitwarden client apps (web, browser extension, desktop, and cli).

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year68 dated mentions

Observed mentions: 2016-10-10 17:59:06 UTC to 2026-08-13 19:41:04 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC505
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC826
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC12012
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC13211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC16313
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Bitwarden Client Applications This repository houses all Bitwarden client applications except the mobile applications (iOS | android). Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started. Related projects: bitwarden/server: The core infrastructure backend (API, database, Docker, etc). bitwarden/ios: Bitwarden iOS Password Manager & Authenticator apps. bitwarden/android: Bitwarden Android Password Manager & Authenticator apps. bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization. We're Hiring! Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden. Contribute Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution. Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.
Read the full README on GitHub

What Hacker News says

12 sources
The code for the server is AGPLv3 https://github.com/bitwarden/server , with only things in the /bitwarden_license/ directory being proprietary. The code for the mobile apps is GPLv3 https://github.com/bitwarden/mobile/blob/master/LICENSE.txt The code for the clients is GPLv3 https://github.com/bitwarden/clients These are all copyleft... with a CLA (contributor license agreement). It's the CLA that allows them the ability to dual-license for the server. The VCs must really believe the company can produce a product based on Enterprise sales which would deliver a value North of $1B. And perhaps they can, as Bitwarden as we know it could be considered a strong beachhead to allow them to expand into other auth markets that have high value (hello Okta, Auth0, etc). But this doesn't seem that scary for Bitwarden users at this point.
In Bitwarden raises $100M
I moved from LastPass to Bitwarden a few years back. Bitwarden does win a few kudos points for being free and open source. Unfortunately, Bitwarden is far from perfect either. It suffers from glaring UI problems which the developers have point-blank refused to address, insisting instead that that is how it is supposed to work --which is incredibly arrogant and 'Jobsian'... "You're using it wrong!" Example: * https://github.com/bitwarden/clients/issues/443 * https://github.com/bitwarden/clients/issues/839 * https://community.bitwarden.com/t/persistent-bitwarden-ui-an...
In Ask HN: What is the best password manager for business use?
> bitwarden/clients/issues/1620 (open since Feb 2021) Oh, try with something much worse, and open since Dec 2017 (no, migrating to a new place is no excuse at all to mark the issue as magically resolved) https://github.com/bitwarden/clients/issues/443 Here I made a pretty clear video of the issue: https://community.bitwarden.com/t/persistent-bitwarden-ui-an... Did anyone care? Not that I know of. It's 2022, so that's been 5 years now. I'll keep paying the pro account as long as it keeps working for me, but it saddens me that we still don't have a universally good and free service that can be recommended to lots of non-techies that are still stuck on the old customs of reusing passwords.
In Tell HN: Bitwarden does not export attachments in backups
My experience is that 1P has a lot more polish and consideration for the user (err, I mean before the "8" debacle). I cannot recall a single time I have lost an autogenerated password, whereas with BW it happened about 50% of the time. Filling up my vault with hundreds of unnecessary password captures is better than losing a single one, because they don't know how important any one password is in order to gauge how "oops, sorrreeee, our bad" affects the user https://github.com/bitwarden/clients/issues/1620 (open since Feb 2021) Aside from that, 1P has a ton more item types, which if one thinks about a password manager as a key-value store, maybe that's not interesting, but for me it's been really great having passport details in a specific spot, without having to invent my own taxonomy for squeezing passport details into key-value pairs S
Read the rest
peaking of taxonomy, BW's lack of tagging is a dealbreaker for me. Why in the world do I have to pick just one "folder" for an item to live in: it can be "work" *and* "aws" *and* "testing" allowing me to see all work, all aws, all testing items grouped together I do hate the new 1P api-only approach, but I'm not going to jump ship just yet because the competition is not yet better for my needs
In Tell HN: Bitwarden does not export attachments in backups
Looking at the export code: https://github.com/bitwarden/clients/blob/da5e4a57d026e0d093... The entire export process seems to be client side. Altering the export to include files should be feasible though the Bitwarden devs might choose not to merge your code because allowing users to access all of those Azure buckets all at once must come at a significant cost. My workaround for this is to stuff SSH keys and the like in secret fields rather than attachments. This doesn't work for larger files, but it works well enough for my use cases so far.
In Tell HN: Bitwarden does not export attachments in backups
I wholeheartedly agree with the UX comment, and for the "leveling up security" part specifically, I'll point out that 1P 8 now has a "generate horse-battery-stable 'security question' answers" button, which is about as close to the intersection of good UX and good security as I can imagine My experience with Bitwarden is that their browser extension is gravely broken, which is a subset of UX, but crosses over into "how is this not a 'stop all work and fix it' bug?": https://github.com/bitwarden/browser/issues/1620 I have a paid Bitwarden subscription, because I wanted to give it a fair shake, but based on my experience thus far it'll be years before they catch up to AgileBits
In 1Password Has Raised $620M

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.