| ▲ | bmitch3020 21 hours ago | |
> Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I've seen more and more PRs where when questioned about how the issue affected the submitter, they replied that they weren't even a user of the project. There are way too many drive-by AI submitted PRs now, where it's clear the submitter is farming for reputation. It's also happening in security vulnerability reports. I'll see reports that start with "assume your package repository is malicious" and report a blind http redirect where if lots of those requests happened to be queued up you may be able to port scan a private network. And I'm like, my dude, a malicious package repository is by definition a remote code execution on every client, stop wasting my time. Until GitHub introduces a way to track how many issues, PRs, and security reports the user submitted that were rejected as invalid, and publicly labels users wasting maintainer time, this problem is going to keep getting worse. Maintainers are going to burn out or delegate maintenance to an AI until quality degrades. Neither of those are good for the open source ecosystem. | ||