How to filter out vibe-coded dependencies

Maybe they did (and ramp’s leadership seems strongly pro-vibecoding, so the odds are pretty good). But, there’s no hard evidence, as far as I can tell. For the topic of vibecoded dependencies, it would be good if there was an example (not necessarily in Haskell) of a regression being caused by a vibecoded PR that got merged. Here’s an almost good enough example (summary: PR with vibecoded assembly that is slower than C). However, in this case, the PR was not merged, so one could make an argument that maintainers do a good job of keeping out bad AI-generated PRs. It would be better if there was an example where the vibecoded regression was actually accepted.