Exactly this. Furthermore, I would add the following considerations (in no particular order): documentation existence/quality, possible use of CI, reasonable c

Exactly this. Furthermore, I would add the following considerations (in no particular order): documentation existence/quality, possible use of CI, reasonable coverage (if shown/known), use/inclusion in other projects, outward quality/appearance of code (can I read it, could I fix it, could I maintain it), licensing (clear/compatible) — outside of the repo: are there articles about it on the web, are there videos about it on Youtube. It varies depending on what the repo is, and what I might intend to use it for, as to how in-depth I will actually go with each of these. But it's always worth a quick scan. There is much that can be inferred from examining such things. Stars are just a single indicator among many.