Some type of rating system like “Rotten Tomatoes” has for people to rate a package on a scale, with perhaps a “critics” rating, although how someone would be designated as a “critic” or subject expert is somewhat ambigious would be nice, or a checklist of desired attributes and some stats like “lines of code” and some information on how many packages might use the code if it a library or how many users use the code if an application would be nice and far more useful than “number of downloads” (could just be because used in a CD/CI script, etc) or “stars” (too Boolean) . A list of mine I use to try to motivate me to clean up a github repo includes
git repository on WWW (github)
annotated source files with an open license
unit test
make(1) build
fpm(1) build
user manual (on-line)
man-page
app program
demo program for public procedures
developer documents (ford(1))
CI/CD(Continious Integration/Development) verification (github actions)
registered in fpm(1) repository
Maintenance Level (actively maintained, abandoned, bug fixes only, … last date changed, …
would be useful too.
An actual repo (like Netlib if it were more organized) so code is available over extended periods and appears as a “release” would be even more ideal. Display of logos is appealing and can be informative, not just eye candy (see fortran-package-manager · GitHub Topics · GitHub) is useful. The human eye can scan through images very efficiently compared to text and AI image generates make it easier to supply such images.