14
submitted 2 months ago by oftheair to c/AntiAI

We've found it incredibly useful for figuring out what is going on with a codebase.

top 7 comments
sorted by: hot top controversial new old
[-] TootSweet@lemmy.world 5 points 2 months ago

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)
  • empty catch blocks
  • promise .catch() default fallbacks
  • generic status envelopes
  • generic record casts
  • stringified unknown errors
  • pass-through wrappers
  • duplicated test mock/setup patterns
[-] Lumelore 7 points 2 months ago* (last edited 2 months ago)

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 6 points 2 months ago
[-] oftheair 2 points 1 month ago

would be funny if it was the correct repo. Thankfully it isn't: https://codeberg.org/polyphony/repo-slopscore

[-] oftheair 1 points 1 month ago

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 points 1 month ago
[-] oftheair 2 points 1 month ago

Ah, fair. We vaguely remember it being absent and seems like the link you provided confirms it, thank you.

this post was submitted on 04 Jun 2026
14 points (100.0% liked)

Anti-AI

132 readers
1 users here now

Fed up with seeing Generative AI trash everywhere? Us too. This is a community specifically for those who hate Generative etc AI and want to put a stop to it.

Rules:

#NoBot #NoAI #NoBridge

founded 5 months ago
MODERATORS