The performative closing of public contributions citing the slop scare felt disingenuous from the start. You couldn't be bothered to implement _any_ mitigations that leave the community engaged with the project?
Writing a contributor karma bot, moving to a non-social or obscure git forge (most slop contributors are resume farming and GitHub is the only forge the HR cares about), newbie-unfriendly non-public workflows like git send-mail, or references from Discord... This isn't an AGI on the other side of the screen, planning the perfect strategy to infiltrate your project; it's a sub-script-kiddie trying to fill a portfolio with quick "contributions" doing the more annoying version of "fixing typos" in docs.