How to filter out vibe-coded dependencies

arybczak: > Exactly. What’s the difference between a package that was badly coded by an LLM and a package that was badly coded by a human? I don’t see any. So perhaps (derailing the particular task the OP set out to solve) we should look for established measures of code quality in other ecosystems. I presume much literature has been written on that subject. In one particular ecosystem I happen to know a little, a linter is marketed that gauges * Mc Cabe Complexity * Code lines per source file / Libs * Code lines per function * Number of functions per file / libs * Number of parameters per function * Number of files per folder * Dead code These metrics could help to detect LLM slop as well as sloppy human coders alike. There is a study that has produced promising results. Once the LLMs adapt and write well-organized, maintainable code to subvert the sloppiness filters, we can declare a victory.