Yeah. I've never done that. I can see the value in it, though.
Personally, I do a Kagi search, or I make an LLM do it for me.
I highly prefer word-of-mouth recommendations like Reddit, HackerNews, or Lobsters. It's quite easy to browse threads where people mention hating some package and switching to something else. It's also a lot easier to see gamified posts (astroturfing), whereas it's really hard to judge projects on GitHub. So many forks are distractions, and stars mean so little. As such, I highly value a personal blog post.
Similarly, I look at what the projects I find link to. They'll often be "inspired by" another project, or a rewrite in a different language. It's a great way to see how different creators consider trade-offs between different projects.
I only browse someone's GitHub when I see an insightful blog post, and I want to learn more about the author and what they work on. Usually I close that tab within 10 seconds cause I can't be bothered to figure out which of their 100 repos is interesting.
My best analogy is that GitHub is the TripAdvisor/Yelp/Google Reviews of finding a good restaurant. Those platforms have been gamified aggressively. The signal is low, and you can't flatten judgement of a restaurant into a 1-5 star scale. Your best bet is to find opinions tied to real people that aren't tied to points.