How vibecoding is destroying the open source that feeds it
Vibecoding, the practice of generating software through natural language prompts to AI, is rapidly growing but poses a significant threat to the open source ecosystem. As developers rely on AI-generated code without understanding or contributing to the underlying projects, contributions to open source have drastically declined. This trend has created a generation of users who consume open source resources without engaging with or supporting the community.
- ▪Contributions to mid-size open source projects dropped 35% between January 2025 and January 2026.
- ▪The number of new contributors to foundational projects has decreased by 41%.
- ▪Vibecoding users often do not know which libraries they are using and do not contribute back to the projects.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/ndabene/how-vibecoding-is-destroying-the-open-source-that-feeds-it-e5f |
| Publication time | Thu, 28 May 2026 21:15:04 +0000 |
| Retrieval time | 2026-05-28T21:29:38.368Z |
| Last seen | 2026-05-28T21:29:38.368Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | RqV2EslVu4jT |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3605489) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Nicolas Dabene Posted on May 28 • Originally published at nicolas-dabene.fr How vibecoding is destroying the open source that feeds it #vibecoding #opensource #ai #development How vibecoding is destroying the open source that feeds it March 3, 2026 The snake eating its own tail A year ago, vibecoding was a curiosity. Today, it’s an industry. Millions of developers — or rather prompters — generate entire applications by describing what they want to an LLM.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).