Marking a project as "dead" because of a lack of activity is IMO a bad approach for a best-of list.
There can (and will) be cases where a project simply doesn't require that much maintenance. Either because the project doesn't have a lot of code to maintain (or none at all if it is about markdown or similar), the code is simple enough to not have a large chance of bugs appearing, or any used APIs/upstream stuff is stable enough to not cause too many bugs (and in most cases only bugs the upstream needs to fix).
Even if you now give the argument that issues and discussion activity are included in the repo being "active" is this still bad.
Projects may have different places where they collect issues and discussions, be it because it's more central (Allowing multiple projects they have to keep one central issue tracker) or because it's what they used before.
I myself saw a few projects that redirect issues through a separate page, so this isn't uncommon.
So, with this issue would I like to do two things:
Propose the addition of options to either disable the "inactive" and "dead" checks completely, or change the displayed output (the emoji) and/or description.
Start a discussion about the proposed idea and what possible alternatives are.
Right now are you calling projects "dead" based on some arbitrary number that may not count towards all projects... And that should be changed in some way.
Marking a project as "dead" because of a lack of activity is IMO a bad approach for a best-of list. There can (and will) be cases where a project simply doesn't require that much maintenance. Either because the project doesn't have a lot of code to maintain (or none at all if it is about markdown or similar), the code is simple enough to not have a large chance of bugs appearing, or any used APIs/upstream stuff is stable enough to not cause too many bugs (and in most cases only bugs the upstream needs to fix).
Even if you now give the argument that issues and discussion activity are included in the repo being "active" is this still bad. Projects may have different places where they collect issues and discussions, be it because it's more central (Allowing multiple projects they have to keep one central issue tracker) or because it's what they used before. I myself saw a few projects that redirect issues through a separate page, so this isn't uncommon.
So, with this issue would I like to do two things:
Right now are you calling projects "dead" based on some arbitrary number that may not count towards all projects... And that should be changed in some way.