Totally fair concern, and I agree that "automate it away and forget about it" is a fast path to a team full of posers. Couple of clarifications on how we use t

Totally fair concern, and I agree that "automate it away and forget about it" is a fast path to a team full of posers. Couple of clarifications on how we use this: • It is not “modern looking = good." A repo with years of steady commits on an "ugly” legacy app can score very high if there is depth, complexity, and real usage. • We explicitly look for things like long term maintenance, non trivial diffs, real world integrations, and documentation, not just shiny landing pages. • The output is a signal for a human, not a gate that replaces one. It helps a recruiter who sees 200 links decide which 10 are worth a closer look. In other words, it is meant to reduce noise, not replace judgment. If someone is quietly maintaining a critical FOSS project, they should stand out more, not less