Linux kernel memory-management code reviewer steps down due to influx of AI slop patches — volume of submissions coupled with low manpower forces the step back
According to the lead Curl developer, the quality of LLM generated reports has gone up quite a lot, to the point where the number of high quality reports is the problem, rather than the number of slop reports: https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/
However, I doubt that their bug bounty program is ever coming back. As you say, that’ll just attract the people looking for a quick buck, and those are unlikely to care about the quality of their reports
The link I posted is to the Curl maintainer’s own blog, in which he wrote a follow-up to his earlier post about shutting down their bug bounty program. See also this more recent blog post by the maintainer of Curl, in which he writes that
I personally don’t refer to [vulnerability reports created with the help of AIs] as AI slop because the reports are typically accurate and correct, even if much too wordy. I think “slop” implies that it is wrong, misleading or otherwise bad content.
According to the lead Curl developer, the quality of LLM generated reports has gone up quite a lot, to the point where the number of high quality reports is the problem, rather than the number of slop reports: https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/
However, I doubt that their bug bounty program is ever coming back. As you say, that’ll just attract the people looking for a quick buck, and those are unlikely to care about the quality of their reports
That is not what the maintainer of curl said, lmao
This article explains the actual situation.
The link I posted is to the Curl maintainer’s own blog, in which he wrote a follow-up to his earlier post about shutting down their bug bounty program. See also this more recent blog post by the maintainer of Curl, in which he writes that