The code is open-source, nobody is hiding the "real state of the software".
"Production-ready" means different things to different people. For many, "production-ready" means "we have a support contract with the software vendor". In that case, the project would never be usable in production. To others with higher risk tolerance, a 1.0.0 release is all you need! You'd have to consider each user before making a recommendation about production-readiness.
Instead the author offers the software AS-IS and you can decide for yourself. The author doesn't owe anyone anything, least of all a personal consultation about whether using the software is prudent.
"Production-ready" means different things to different people. For many, "production-ready" means "we have a support contract with the software vendor". In that case, the project would never be usable in production. To others with higher risk tolerance, a 1.0.0 release is all you need! You'd have to consider each user before making a recommendation about production-readiness.
Instead the author offers the software AS-IS and you can decide for yourself. The author doesn't owe anyone anything, least of all a personal consultation about whether using the software is prudent.