I knew someone would say that haha. Let&#x27;s rephrase what you said in a general context to show what the problem is:<p>&quot;Anytime you&#x27;re evaluating solutions to a specific problem in your system or code you should look at all the source code people are posting without expecting a description of what it does. Just read all the source code out there, guess if it meets your needs, and then try whichever looks right.&quot;<p>Kind of dumb way to go about finding 3rd party libraries or tools. Similarly foolish to expect it unless one simply doesn&#x27;t care about adoption at all. The alternative, which my comment promotes, is to have relevant data in a short summary on each projects&#x27; page. Google, HN, or whatever finds users&#x2F;developers a set of pages like this. At a glance,  they can tell what&#x27;s worth further investigation. Then, they look at its code. <i>Much</i> better way to use limited time to find needles in the massive haystack that is the Web.