Ask HN: How do you handle PR density (and slop) in open source
Given that coding agents like Claude Code or Codex are now quite good, there's of course a massive increase in PRs submitted to open source projects. Not all of them are great, some are true AI slop.
See for example Daniel Stenberg on the topic as it relates to cURL: https://daniel.haxx.se/blog/2026/01/26/the-end-of-the-curl-bug-bounty/ and https://daniel.haxx.se/blog/2025/07/14/death-by-a-thousand-slops/
I'm curious how much of a problem this is to other open source projects
Committers, how much of this pain are you seeing, and are you using any AI tools to mitigate or address this issue? The cURL situation is a canary. The real fix isn't gate-keeping humans out, it's making quality enforcement automatic before a PR is ever opened. I built LucidShark specifically for this: it's a local CLI quality gate that runs SAST, SCA, linting, type checks, coverage, and duplication analysis in one shot on AI-generated code.