Brave forked kuchiki to kuchikiki because it wasn't actively maintained. Now kuchikiki is not actively maintained. So do I fork again to kuchikikiki?

Brave originally forked kuchiki because it wasn't actively maintained. Now their fork, kuchikiki is not very actively maintained. I think this is unfortunate. If anyone, especially a company, attempts to take ownership of a project and tout it as a replacement, I'd hope they would be serious and wouldn't just drop it so soon.

On the surface it may look "maintained" since the last commit was 3 months ago. But commits the last 2 years have only been maintenance bot PR's, while community PR's and issues have been sitting for years without comments. This is pretty small library in the grand scheme, but many downstream libraries depend on it and using my fork and patching dependencies is starting to no longer work as dependencies like cssparser, html5ever, and selectors api's evolve and other libraries still depend on the current version of kuchikiki or the speed-reader version. And Brave won't update dependencies or look at issues that effect users.

Honestly I know in open source they don't owe developer time to anyone, but I wish they never tried to take ownership of kuchiki and left that to another community member who would actively maintain the crate. It makes sense why the original crate owner refused to hand over the crate to them.

I don't want to fork (kuchikikiki sounds ridiculous) and fragment the community more. But just frustrated by the situation.