How to filter out vibe-coded dependencies

I think Haskell won’t really have this problem. And that’s a good and bad thing. Good because it means the ecosystem will stay relatively manageable bad because it’s indicative of low/waning interest in the language/ecosystem. I’ve been keeping a pulse on the Google summer of code mentors discussions and organizations are receiving record numbers of PRs and record numbers of applicants clearly fueled by AI contributions. There’s been pretty long discussions about how maintainers feel overwhelmed in other ecosystems. Meanwhile Haskell had roughly the same number of applicants (in fact less than last year) and the ones who contributed code to as part of their applications seemed thoughtful and honest in their use of AI. So we don’t attract that many people but the people we do attract tend to be the “right” kind of people for now. I think the AI discussion is important to have because if the community grows at any point in the future it’s better if our stance is clear. That said, I’ve said this in other threads too, getting people to adopt Haskell is hard enough because of its perceived elitism so name and shame lists might not be great if attracting new developers in the goal. Maybe softer ways to nudge people to focus on high quality contributions might be a better strategic and political investment. Idk what that looks like.