HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
keepassxreboot
keepassxc
C++2017–2026
keepassxreboot / keepassxc

keepassxc

KeePassXC is a cross-platform community-driven port of the Windows application “KeePass Password Safe”.

147Distinct people
211Mentions
2Explicit recommenders
30KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

KeePassXC is a cross-platform community-driven port of the Windows application “KeePass Password Safe”.

GitHub

Where it is used

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

What people are saying

I love that the "big guys" get to support syncing passkeys between devices... but others don't (wasn't it KeePas who had issues where they were threatened by being blocked from…

FireBeyond used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:28:18 AM 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 year211 dated mentions

Observed mentions: 2017-01-19 23:33:12 UTC to 2026-10-14 23:38:36 UTC.

010203040502017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 19 mentions; 1 submissions, 18 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 24 mentions; 2 submissions, 22 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 47 mentions; 3 submissions, 44 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 45 mentions; 0 submissions, 45 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 37 mentions; 0 submissions, 37 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
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC19118
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC707
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC10010
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC716
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC707
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC24222
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC47344
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC45045
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC37037

From the project README

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

Read the project’s introduction
KeePassXC KeePassXC is a modern, secure, and open-source password manager that stores and manages your most sensitive information. You can run KeePassXC on Windows, macOS, and Linux systems. KeePassXC is for people with extremely high demands of secure personal data management. It saves many different types of information, such as usernames, passwords, URLs, attachments, and notes in an offline, encrypted file that can be stored in any location, including private and public cloud solutions. For easy identification and management, user-defined titles and icons can be specified for entries. In addition, entries are sorted into customizable groups. An integrated search function allows you to use advanced patterns to easily find any entry in your database. A customizable, fast, and easy-to-use password generator utility allows you to create passwords with any combination of characters or easy to remember passphrases. Quick Start The QuickStart Guide gets you started using KeePassXC on your Windows, macOS, or Linux computer using pre-compiled binaries from the downloads page. Additionally, individual Linux distributions may ship their own versions, so please check your distribution's package list to see if KeePassXC is available. Detailed documentation is available in the User Guide. Features List KeePassXC has numerous features for novice and power users alike. Our goal is to create an application that can be used by anyone while still offering advanced features to those that need them. Core Features Create, open, and save databases in the KDBX format (KeePass-compatible with KDBX4 and KDBX3) All information is encrypted at rest and never exposed outside the program Store sensitive information in entries that are organized by groups Password generator Search for entries TOTP storage and generation YubiKey/OnlyKey challenge-response support Auto-Type passwords into applications Browser integration with Google Chrome, Mozilla Firefox, Microsoft Edge, Chromium, Vivaldi, Brave, and Tor-Browser Support for passkeys using the browser integration Entry icon download Import databases from CSV, 1Password, Bitwarden, Proton Pass, and KeePass1 formats Advanced Database reports (password health, HIBP, and statistics) Database export to CSV, XML, and HTML formats TOTP storage and generation Field references between entries File attachments and custom attributes Entry history and data restoration Command line interface (keepassxc-cli) SSH Agent integration FreeDesktop.org Secret Service (replace Gnome keyring, etc.) Additional encryption choices: Twofish and ChaCha20 For a full list of changes, read the CHANGELOG document. For a full list of keyboard shortcuts, see KeyboardShortcuts.adoc Building KeePassXC Detailed instructions are available in the Build and Install page and in the Wiki. Contributing We are always looking for suggestions on how to improve KeePassXC. If you find any bugs or have an idea for a new feature, please let us know by opening a report in the issue tracker on GitHub, or join us on Matrix community channel or Matrix development channel, or on IRC in Libera.Chat channels #keepassxc and #keepassxc-dev. You may directly contribute your own code by submitting a pull request. Please read the CONTRIBUTING document for further information. Contributors are required to adhere to the project's Code of Conduct. Generative AI Generative AI is fast becoming a first-party feature in most development environments, including GitHub itself. If the majority of a code submission is made using Generative AI (e.g., agent-based or vibe coding) then we will document that in the pull request. All code submissions go through a rigorous review process regardless of the development workflow or submitter. License KeePassXC code is licensed under GPL-2 or GPL-3. Additional licensing for third-party files is detailed in COPYING.
Read the full README on GitHub

What Hacker News says

24 sources
I'm not sure about any specifics beyond that both are getting support for them (for the keepass ecosystem I'm sure about other mobile clients, but I don't think the feature request to support passkeys has been acknowledged by the keepass2android dev sadly). Here's the keepassxc PR with some details about the implementation, and what should be done in future work on passkey support: https://github.com/keepassxreboot/keepassxc/pull/8825 Bitwarden has a few blogs if you search for bitwarden passkeys, but from skimming one it didn't seem to go into technical details (though I didn't watch the videos). I guess you could look through the PRs: https://github.com/bitwarden/clients/pulls?q=is%3Apr+passkey... but I don't really feel like doing that.
In 23andMe says user data stolen in credential stuffing attack
Because the goal of WebAuthn is to not depend on any companies infrastructure. And there's work being done in that direction. Apple supports passkeys from third-party password managers, 1Password has a Passkey beta and KeePassXC has a pull request working on passkey support. [0] That independence is a design goal of passkeys, because they want to replace passwords and passwords are independent by their nature. [0]: https://github.com/keepassxreboot/keepassxc/pull/8825
In What is the origin of passwords submitted to honeypots?
https://github.com/keepassxreboot/keepassxc/pull/2292#issuec... became https://github.com/keepassxreboot/keepassxc/commit/125a81f2e... for some inexplicable reason. Now it looks like droidmonkey authored that entire feature. I did see the "squashed commits" and "taken under my wing" part but it appears it was a `git add .` and not a `git rebase` type operation that would have preserved the original author separate from the committer I mean in the end I'm not jammed up about it because my objective was to contribute back the local patches I made to scratch my itch, but it means I have to remember the PR number because that's the only evidence of my authorship
In Rejected GitHub profile achievements
You can always use a FIDO2.1 key as a passkey, they're not tied to the big tech. I don't even have a smartphone and have been using them on the couple of sites that support passkeys just fine. We will also have at least one open software implementation when this gets merged: https://github.com/keepassxreboot/keepassxc/pull/8825 There are braindead implementations like PayPal's: https://www.paypal.com/us/cshelp/article/what-are-paypal-pas... that force you to use Android or iOS, but it's nothing new, they manage to fuck up everything they touch (for example, U2F 2FA only supports registering one hardware key and it has been that way for years).
In Passwords Are Fine
I Use KeePassXC[0] on the desktop and is really great. It is open-source; not an Electron app, it is written in C++[1]; there are browser plugins to auto-fill user/password/TOTP codes; it is local-first: not tied to any cloud vendors and you can easily sync the database file via any cloud system if you want; there is an Android app that can use the same database. [0] https://keepassxc.org/ [1] https://github.com/keepassxreboot/keepassxc
In Proton Pass end-to-end encrypted password manager is here and free for everyone
> KeePass does today Not yet: https://github.com/keepassxreboot/keepassxc/issues/8214 (and https://github.com/keepassxreboot/keepassxc/pull/8825) And even if they will, they're at mercy of e.g. Apple letting anyone to replace iCloud Keychain with a third-party password manager. Which is also not possible yet. Probably the same for Android, although I'm not sure what's the situation there today. (But whatever it is, I would say that "well, don't use Apple/Google devices" is not an option for many in the current duopoly.) All this can be solved, but the issue that is is not - today. So, today, I'm voicing my discontent. > and then you can use your password manager as your Passkeys provider on all your devices In an ideal world - yes. Sadly, I can't do this today with passwords, even though the world had spend many decades on trying to make
Read the rest
things as seamless as possible. Over last year I've had to manually open a password manager on one device and type a password on another more than a few times. The most obvious example is logging in to a streaming service on a smart TV - one step away from the normal conditions (scan-QR-code-on-my-phone flow not working) and typing password is the only option. Netflix is gonna love passkeys so users will possibly have slightly harder time logging in on others' devices ;-) BTW, sharing passkeys is also not exactly a solved issue - yet (even though some vendors made some promises). Then, there's a case of accessing from untrusted devices (say, a net cafe). Theoretically, Passkeys should be a drastically superior solution to passwords - I would be able to plug in a security key, and it won't leak the keys, so even if a machine has a keylogger or network sniffer I'm still fine. In practice, however, enrolling a physical security key (Yubikey, Nitrokey, Solo) requires having it physically available, so it's always going to be inconvenient - and this is not changing until the standard extends or changes. Worse for multiple keys (I have four so every Webauthn sign-up is a pain in the ass). Because I'm most certainly not installing my password^W passkey manager on some untrusted machine.
In Tailscale doesn't want your password

Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.

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.