Ask HN: How do you evaluate the reliability of an open source project

Was curious about this as I've recently had an issue where a project I was working on used a library which was chosen due to being regularly mentioned across various online sources as a good solution, and had a strong star rating on github. However, it ultimately appeared to have stalled in development over 2 years ago and the primary contributors were very vague about their roadmap beyond announcing that they had one and likely just don't have the time to work on the project themselves any more.

Are there any warning signs that put you off adopting an open source project beyond the quality of the code and documentation? (e.g. number of forks on the Github repo, number of issues, frequency of releases).