Do you know why they have been stalled? Perhaps there's a good reason, like code auditing? Just a shot in the dark - I have no idea.

Judging from TFA it's due to KeePassX having one maintainer, so the pull requests all bottleneck with him. Also mentioned is that one desirable outcome of this is that KeePassXC developers are given co-maintainer status of KeePassX and that they re-merge down the line.

That's cool. But if that's all this project is, couldn't they have just talked to the one maintainer and offer to help him and be on the team?

https://github.com/keepassxreboot/keepassxc/issues/43 states the maintainer hasn't been commenting on PRs. I looked on the keepassx GitHub and some issues with no response are over 2 years old.

I wonder how often those conversations take place before someone(s) fork a project because it's "abandoned".

But I love KeepassX and I'll certainly try using the fork.

I would assume that avenue has been tried -- so this project is to pressurise him into opening up to the idea. No idea though.