The reasons for the fork are explained in details there: https://github.com/keepassxreboot/keepassxc/issues/43#issuecomment-254045934 https://github.com/keepass

The reasons for the fork are explained in details there: https://github.com/keepassxreboot/keepassxc/issues/43#issuecomment-254045934 https://github.com/keepassxreboot/keepassxc/issues/43#issuec... It is rather worrying that they mention "keypasshttp" as being one of the pull request which was never merged, although it is all about functionality and not security, just to point out a few months after in another issue that users should stop using this plugin because of a vulnerability: https://github.com/keepassxreboot/keepassxc/issues/147#issuecomment-272525411 https://github.com/keepassxreboot/keepassxc/issues/147#issue... I don't really know how secure KeepassX is, but this fork doesn't look like it is any more secure, at least for the time being.