To say that open source is being killed by vibe coding is just... crazy. It's simply wrong.
There are numerous vibe coding apps now which were written entirely with vibe coding. An entirely new paradigm of development exists today which didn't exist even a year ago - claude code, opencode (omo/slim), codex, cursor, and on and on. Then you've got the agentic stacks, and everything else that's largely open and free. "Come use this vibe coded thing I built this weekend! It's live in production, you can see it working - and here's the git repo!"
Coding skills are no longer a barrier to iteration and improvement. There are so many cool projects out there now being done by people who have an idea and see a business case and want to fill it.
Aside from the projects, I've already taken 2 libraries myself and forked them to change (and improve) functionality for my specific use cases. I'm assuming they don't want my changes, but they can always pull them back if they want. They can see I've got a fork. My willingness to deal with "well they may not accept my changes" + slowing my own velocity is low. The repo is public, the commit comments are better than anything I've personally done in the past.
"AI and vibe coding breaks that process at the early stages because there is no longer the humans looking at new things and taking a chance on something new and unfinished"
Um... have you even tried vibe coding? You can one-shot a project in 20 minutes. I've done it numerous times - an old project I spent weeks writing specifications for, boom, done. I also now have a very useful data indexer which integrates smb shares with MacOS finder. Any sort of idea can now quickly come to fruition in a couple hours with a good set of prompts. Want to make an antiquated database format convertible to a newer platform, and reimplement the frontend? I once had to take a 15-year old physical SCO system running a proprietary database over to a virtual environment, 10 years back. It was a painful process, because SCO and failing hardware. But today? Once I got to that point I could've reimplemented it anew in a couple days, allowing those companies to expand the software capabilities they paid hundreds of thousands for at the time, to something which suited their current business needs (which were a paper and spreadsheet process).
A mildly capable office tech could take an existing git repo of their project tree and maintain it/add features and maintain the product well enough using vibe coding, instead of languishing for a decade, like they had to previously.
You seem to be missing the fact that LLMs have vastly exceeded prior functionality. Today, the frontier models are easily 2x what they were in October. October was easily 2x what they were in May of last year. May of last year? 2x as capable as they were the year prior. We're approaching exponential improvements, and models have been solving previously-unsolved NP hard problems: that's innovation.
If you have an idea, it can be done with vibe coding today if you have the intelligence and creativity to do it. Simple as. If you don't, you can't - and won't.