How to filter out vibe-coded dependencies

I’m sympathetic to the concern. The category difference between generation prior to LLMs is that: * it was almost always clearly marked (pgmF, template haskell, the glib-gens, etc) with limited scope, and * as a result, the output was predictable and regular, so no one ever said “I dunno, it was generated” in a deferential way LLM use flips both of these, where it is unlimited in scope, not clearly delineated, and many (not all, but I’ve seen smarter devs than me) become deferential with a sense of justified ignorance. “I don’t know how it does what it does, why it’s like that,” both to peer review and when a bug happens. Neither of these are surprising, but it does change the relationship and the social contract (open source is primarily a social thing) between people in a real way, regardless of any value judgment. I’m neutral on LLMs, they obviously have power and obviously have a cost (medium is the message, etc). How to recognise, manage and mitigate that while retaining quality, joy, personal stake, etc. within a community seems like a reasonable thing to start pondering openly. Apologies if this doesn’t advance the discussion, just wanted to say it’s on my mind too, @hasufell.