I've seen enough security bugs that I don't want to trust the gut feelings of a non-expert, such as myself. One example I can think of is another password manager that used random numbers incorrectly putting a bias in the random passwords it was generating.
Which is not to say it's a bad idea to get expert vetting for something like this (it's obviously an ultra-safe approach), but it helps to try to put things in context yourself, so that you don't have to find an expert every time you need to make a security decision. In the context of a desktop password manager, there isn't a terrible lot that can go wrong by accident and suddenly result in password exposure once the core product is formed and secure. If it happens, it'd be almost certainly due to a new maintainer coming along and somehow checking in unsafe code, rather than the current maintainers (say) suddenly forgetting they shouldn't call rand() or accidentally saving plaintext passwords on a disk.
KeepassX is no longer maintained.
KeepassXC is maintained and more featured, it's also not dependant on .NET.
KeypassX is a rewrite in C++, using QT. KeypassXC is a fork of KeypassX, as KeypassX was felt to be unmaintained.
KeypassX was abandoned 3 years ago
There is also keepassxc-cli and kpcli.
Important accounts are sharedd between my wife and I, and I back everything up to my NAS regularly.
For work, we're looking in to vault by hashicorp.
I've lost a lot from KeepPassX by being spoiled by other auto-saving managers over the majority of this century.
KeePass saves passwords in a single encrypted file by default. This means that an attacker has no idea about the structure of your entries and usernames.
Plus, it's easier to setup on multiple machines, as you don't need to export/import your PGP keys from your initial machine.
Features and ease of use are subjective to each user.
