How to filter out vibe-coded dependencies

Personally, I share the sentiment somewhat and indeed want to set a boundary like that.

Alas,

1. This smells strongly of “solving a social problem with tech”, and I’m worried this wouldn’t work (or at least be a net positive all things considered).
2. This seems to punish cooperation and promote goodharting. Being honest and open results in having to deal with being flagged. Go dark to avoid dealing with more stuff in your life.
3. The criteria, the lists, and the whole endeavor seem to induce even more fragmentation (on the code level) and tribalism (on the social level).

(Not to derail the thread or induce scope creep (sorry, I’m about to do just that).) I’d like to have some place where I can annotate (privately, and this is critical IMO) packages and their authors with labels for maintainership, correctness, perf, vibecodededness etc. Then run estimations on that annotated graph like “Would I regret adding this package to my dependencies?”