If the underlying code looks solid and useful to me, then I might try to use it. But in most cases, I keep looking for something that is reasonably lively.
The key thing I keep in mind is that open source means that the developers primarily wrote the software to scratch their own itch. In time priorities change and it is unreasonable to expect them to support something they have lost interest in. In most cases, "better" solutions have emerged and thence their loss of interest.
This is exactly where organized open source and commercial open source (COSS) products come into play.
They're supported by an active community, funded by the users (and investors at times), and companies don't run out of resources to maintain and scale what's helping the primary user-base.
I help support open source projects that are leveraged by those with disabilities. Often those individuals can't contribute back as they are focused on there careers/ day-to-day life leveraging the project. So on boarding diversified people outside of that segment an would add valley to the talent pool of the project.
The 2 big problems are: 1) Discovery (Knowing the right tools)
2) Friction to use Open source, self host, understanding documentation... - Even trying one tool takes a lot of effort to use the tool.