I googled a bit (actually DuckDuckGo'd) to find the source code of that tool because I wondered what it considered "evidence", and I believe this is it. Looks like it looks for:
log-and-continue catch blocks
error-obscuring catch blocks (default-return or generic replacement error)
Seems more like a bad coding practice detector than an AI detector. Although obviously one would expect AI code to be more sloppy. I often do log-and-continue catch blocks myself with the intent of coming back to do better error handling later, but often times I don't because I forgot or am lazy or don't care.
7 Comments
TootSweet@lemmy.world · 4 pts · 78d
I googled a bit (actually DuckDuckGo'd) to find the source code of that tool because I wondered what it considered "evidence", and I believe this is it. Looks like it looks for:
Lumelore@lemmy.blahaj.zone · 6 pts · 78d
Seems more like a bad coding practice detector than an AI detector. Although obviously one would expect AI code to be more sloppy. I often do log-and-continue catch blocks myself with the intent of coming back to do better error handling later, but often times I don't because I forgot or am lazy or don't care.
rimu@piefed.social · 4 pts · 78d
lol
oftheair@lemmy.blahaj.zone · 2 pts · 51d
would be funny if it was the correct repo. Thankfully it isn't: https://codeberg.org/polyphony/repo-slopscore
oftheair@lemmy.blahaj.zone · 1 pts · 51d
We guess you missed, or it wasn't there at the time, the button that says source code on the site: https://codeberg.org/polyphony/repo-slopscore
TootSweet@lemmy.world · 1 pts · 51d
Yeah, it wasn't there at the time. Looks like I found the wrong repo.
oftheair@lemmy.blahaj.zone · 2 pts · 51d
Ah, fair. We vaguely remember it being absent and seems like the link you provided confirms it, thank you.