I am wary of adding too much information that relies on Github APIs because 1. it encourages centralization on a proprietary platform

Couldnt agree more! This is why I decided not to use discussions or issue count since those are GitHub specific. Commit count could be gathered from any platform that uses git.

2. we are already running into API rate limits with just the info we currently gather (stars count + last commit date).

Im using the GitHub GraphQL API to query all necessary information for 100 repos at a time, including commit count per month. The rate limit for GraphQL is allowing up to 5000 points per hour and on of these queries only costs 1 point. Herre is my code to generate the query: https://github.com/mkitzmann/awwesome/blob/main/src/lib/query.ts

And we would need a way to store this graph information in the raw YAML data somehow. If you want to create an issue for this, to gather more feedback and so it can be discussed further, please do!

The Informationen is currently just „{month: count,…}“, so should be fairly simple to store in yml. I will create an issue for it.

Very sorry for the missing attribution. I added it in the header, should be online now.

Just want to say that Im a big fan of what you guys do! Awesome Selfhosted is really great.

Regarding the topics Im also not 100% happy with it but at least it provides the ability to find projects that likely support docker for example. It would probably be great to have this kind of information inside awesome selfhosted.

More than happy to add an issue for Icons. The problem here is that repos dont actually have icons, there are only icons from the owner of the repo. So with some projects its a photo of the owner for example.

I looked a bit into how best to determine the activity level of a project and for me commit history is one of the strongest signs. Also Github uses this kind if graph in a users repo overview so its already familiar to GitHub users. There should be a label with the max number of commits to provide some scale, could be a browser problem.

There is also https://isitmaintained.com/ which measures issue resolution and percentage of open issues. But this can also be quite missleading since it shows positive for an empty repo.

Thanks for the link to the generator, I will look into it.

I started working on a similiar project a few weeks ago.

I crawled the old markdown version and then queried the GitHub GraphQL API for some additional info like topics, avatars and commit count over the past year.

Repo: https://github.com/mkitzmann/awwesome Demo: https://awweso.me/

Im more than happy to collaborate on this if there is any interest.