First: The way signals are tracked stays the same. If a repository had 25 AI-generated commits detected before, that'll still be just the same. The only thing that was touched was the way the score (100 (S)–0 (F)) gets calculated.
Instead of treating every detected AI/slop signal equally, slopscore now tracks the share of tainted commits across a repository.
This means: It now makes a significant impact whether the repository is made up of slop commits to 1% or, say, 50%. Repositories with lower slop-densities get gentler penalties, while high-density repos get scored significantly harsher. It just didn't feel right that 10 slop commits got scored the same, whether the repo only had 15 commits, or already had 10000 commits.
This feature has been in beta for a while and the new scoring curve has been tested for a while before it finally got merged and deployed today.
Do feel very free to check out the changes by re-scanning repositories you are curious about, and leave feedback either here, on Zulip or as an issue on the repository!
