> Like, what if you included a library in your project that was vibe-coded (but your main code wasn't), would your project be considered as "human-made"?
Any dependency on a vibe-coded library, however indirect, makes an application not 100% human made (since the application relies on the library for some of its featutes).
If that's going to be your definition, then it's going to be extremely difficult, if not impossible to have a 100% human made program, unless you've personally hand-coded the entire OS, or you've verified beyond doubt that no vibe-coded dependency exist in the entire dependency chain - both build and runtime, direct and indirect.
I'm not sure how feasible verification of that would be, unless we have some "certified 100% human" certification program of some sort, with an external auditing agency or something - because you can't trust humans, they will 100% lie.
If "verifying the entire dependency chain" is that difficult for your project, you have a problem in any case (and you're probably using npm).
You don't need to have personally hand-coded the OS, of course, you just need a OS that's not vibe-coded, and hopefully that just means avoiding Windows.
Even if you actually consider the OS a dependency, which is a stretch
And hopefully vibe coding doesn't get as widespread to become hard to avoid it.
If that's not okay, what if the library included a library which included a library that was vibe-coded?