OK. I use a very similar set of heuristics to what's described in this post.
Here's the documentation for the most recent thing I released:
https://django-registration.readthedocs.io/en/3.0/
And the one before that:
https://pwned-passwords-django.readthedocs.io/en/1.3.1/
Here's the next of my packages that I'm working on, not because the code needs work but because the documentation isn't up to my standards anymore (in fact, I'm doing a rolling refresh of all my personal packages right now):
https://webcolors.readthedocs.io/en/1.8.1/
I don't expect everyone else to match my output in documentation. I do expect people to write some type of prose documentation covering more than just "here's an auto-generated API reference, good luck", or "here's a README with a couple examples, good luck". And I absolutely treat quality of documentation as a predictor for quality of code, because it tends to be a pretty strong predictor.
Want to tell me how "entitled" I am?