Are you tired of having to manually traverse commit histories to find out whether a repository has been made using AI/LLMs?
Uncategorized
10
Posts
6
Posters
0
Views
-
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb -
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb@polyphonychat Can't wait to do funny multithreaded shenanigans; and of course, repo-id based deduping, theming, and other things that are quite obviously needed for the software to be more than a prototype. But hey!! It works, pretty reliably so even, and that's cool :3 -
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb@polyphonychat oh my god, just when I thought I couldn't get more excited about Polyphony, you make stuff like this?
-
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb@polyphonychat oh, i made something similar recently for checking my dependencies too. you may find the lists in commits.rs and files.rs here useful: https://github.com/mat-1/slopcheck/tree/master/src/indicators -
@polyphonychat oh, i made something similar recently for checking my dependencies too. you may find the lists in commits.rs and files.rs here useful: https://github.com/mat-1/slopcheck/tree/master/src/indicators@polyphonychat i also considered making it search the codebase to check the frequency of em dashes but i never implemented that...
-
@polyphonychat oh, i made something similar recently for checking my dependencies too. you may find the lists in commits.rs and files.rs here useful: https://github.com/mat-1/slopcheck/tree/master/src/indicators
-
@polyphonychat oh my god, just when I thought I couldn't get more excited about Polyphony, you make stuff like this?
-
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb@polyphonychat@amazonawaws.com
my only gripe with this is that it scans for
CLAUDE.mdwithout scanning the contents thereof. i have aCLAUDE.mdbut it's meant to sabotage users thereof. -
@polyphonychat@amazonawaws.com
my only gripe with this is that it scans for
CLAUDE.mdwithout scanning the contents thereof. i have aCLAUDE.mdbut it's meant to sabotage users thereof.@swirly Yes; tools like these will never be 100% accurate. I am currently not sure how I'd approach analyzing the contents of a CLAUDE.md or AGENTS.md file to determine whether it is meant to attract or deter LLMs. But the existence of such a file is, in my opinion, a potential indicator for AI activity. As such, it gets reported; but if there aren't any other signals, you'll still have an A+ rating -
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 ofrepo-slopscoreat slopscan.ava.pet, paste inhttps://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 theREADME.mdin our repository!
RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb@polyphonychat thanks for making this
-
R relay@relay.mycrowd.ca shared this topic
