As for “production-ready”, it honestly doesn’t mean all that much. past a certain point. There are tons of projects that stay at 0.x.x versions their entire lifetime, yet are well-supported and perfectly good for production use, and are well worth checking out. Likewise, there are projects that claim to be production ready and use 1+.x.x versions, but have significant issues that can completely prevent you from using it.
You’ll have to put in effort to update dependencies and keep up with breaking changes no matter which framework you choose, so what you shouldn’t be looking for isn’t one that labels itself as “production-ready”, but rather simply look for one that fits your needs and seems popular enough to remain active. The best way to help a framework get “production ready” is by using it in production, identifying problems, opening Issues on the repo, and helping fix the issues that may prevent others from using it.
You obviously don’t want to spend months building something in a framework only to find that it can’t run in your production environment, but it should be pretty easy to identify those kinds of issues early on. So try these frameworks out and get them deployed to a test environment, and you should be able to give yourself enough confidence on whether the framework will fit your needs before you fully commit your project to it.