Fighting AI/LLM slop-assisted/generated code (+)Are you tired of having to manually traverse commit histories to find out whether a repository has been made using AI/LLMs? There's now an easier way!
You can access the first version of repo-slopscore at slopscan.ava.pet, paste in https:// git repo URLs and have it scan repositories for signs of AI activity. The source code is, of course, available at codeberg.org/polyphony/repo-slopscore !
The prototype is most definitely rough around the edges, but also functional! You can read more about how the internals of it work in the README.md in our repository!
Improvement ideas for repo-slopscore; Fighting AI/LLM slop-assisted/generated code (+)I would appreciate feedback on the idea of adding "healing" to repo-slopscore: codeberg.org/polyphony/repo-slopscore/issues/9
This idea is the result of feedback I have received here overnight.
Improvement ideas for repo-slopscore; Fighting AI/LLM slop-assisted/generated code (+)@polyphonychat Now that I've found cases where projects have accepted slop-commits by mistake (and reverted them), I think the concept of healing might be useful. Adding a short date-string next to each evidence might also be useful when showing the "report"
1
1
1