sspaink
commented
9 months ago @powersj how about this....
A dependency can be described with one of these three categories:
- Alive - Has few issues, but actively maintained (e.g. recent commits)
- Zombie - Has multiple problems, almost dead but still slowly moving around.
- Dead - Has been abandoned (e.g. github archived, last commit over a year ago)
A dependency can be assigned into one of these categories based on a weighted grading system, where we define multiple checks. Each check returns a score and a weight. Like what this grading calculator does. Then you can take the percentage and organize it, maybe something like this (random ranges):
- Alive - 70-90%
- Zombie - 30-69%
- Dead - 0-29%
Then depending on how many zombie and dead dependencies your project has, the project then can get an overall rating. Not sure what, something that tells the user that your go mod file has become a graveyard. Maybe this can just be the percentage of zombie and dead?
I think it could be easy to make icons to represent each category. Then you can tell at a quick glance the health of a project.
icon related ideas:
- We could make a VS code extension that displays the icons next to the dependencies in a go.mod file. Then if you click the icon it will give you a report about what checks it failed.
- Github action that checks dependencies and if a bad dependency is being introduced, add a comment with a picture of a zombie
- Github label that shows: normal gopher w/ green background, zombie gopher w/ orange background, gopher skull w/ red background
Watcha think? :ghost:
powersj
Get general process working, run against some sample repos that we know are not maintained or those that are, and see what type of rating makes sense.
For example: