Research · 8 min read

Vibe coding, by the numbers

Everyone has a hot take on AI-built software. The data is more useful than the takes — here's what the surveys and studies actually found, and what it means if you're buying or selling one.

V The Vertos team Updated July 2026

"Vibe coding" went from a half-joking tweet to how a huge share of software now gets written, all in about a year. Whether that's exciting or terrifying usually depends on whether you're the one shipping it or the one buying it. So let's skip the vibes and look at the numbers.

01 · AdoptionIt's not niche anymore

Start with the least controversial number: almost everyone is doing this. In Stack Overflow's Developer Survey, roughly three in four developers said they were using or planning to use AI tools in their workflow, with a clear majority already using them regularly.

~76%
of developers are using or planning to use AI coding tools — with the majority already using them day to day.

That's the important context for everything below: AI-assisted — and increasingly fully AI-generated — code isn't a fringe experiment. It's the mainstream way software gets built now, which means a growing share of the projects that get bought and sold were vibe-coded at least in part.

02 · QualityFaster to write, harder to maintain

Here's where it gets interesting. AI tools unambiguously make code faster to produce. What the data questions is whether that code is as durable.

The most-cited analysis here is GitClear's, which looked at hundreds of millions of changed lines of code as AI assistants rolled out. It found the fingerprints of speed-over-craft: rising code churn (code rewritten or deleted soon after it's added), and more duplicated, copy-pasted code — while the share of "moved" code, the signal of thoughtful refactoring, fell.

Code churnUp

More code is written and then quickly thrown away — a sign of iterating past the target rather than toward it.

Duplicated codeUp

Copy-pasted blocks climbed as assistants made it easy to generate the same thing again instead of reusing it.

Refactored ("moved") codeDown

Less code is reorganized and consolidated — the maintenance work that keeps a codebase healthy over time.

The honest read isn't "AI code is bad." It's that AI is very good at producing a lot of plausible code and indifferent about whether it's clean, deduplicated, and maintainable. Left unreviewed, a vibe-coded project accrues the kind of debt a buyer will find later.

03 · SecurityConfident, and sometimes wrong

The most cautionary finding is about security. In a controlled Stanford study, developers with an AI assistant wrote less secure code than those without one — and, more worryingly, were more confident that their code was safe. AI is fluent, and fluency reads as correctness even when it isn't.

In practice that shows up as the boring, dangerous stuff: missing input validation, weak auth, and — the classic — secrets committed straight into the repo. None of it is exotic. All of it is exactly what a careful buyer checks for before they wire money.

AI didn't make code quality matter less. It made it matter more — because now there's far more code, written far faster, by people far more sure it's fine.

04 · The marketSo — do vibe-coded apps sell?

Yes. A working app with real users and revenue is a real asset, and no buyer worth selling to cares whether a human or a model typed the lines. What the data above tells you is which vibe-coded apps sell — and for how much.

Sells well
Hardened & provenReviewed code, tests, no committed secrets, real traction. The AI was a tool; the result is a clean, transferable product.
Sells cheap
Raw prototypeGenerated in a weekend, never reviewed, secrets in the config, "works on my machine." It might be a great idea — but the buyer is pricing in the cleanup.

This is precisely why serious marketplaces put the code under a lens before a deal. On Vertos, every listing includes a free, automated read of the actual source — languages, dependencies, a readiness checklist (tests, CI, license), and the frameworks and integrations it really uses — so a buyer isn't taking "trust me" at face value, and a seller who did the work gets credit for it. The market rewards proof, and the fastest way to prove a vibe-coded build is to let the code speak.

The quick versionWhat are the key vibe coding statistics for 2026?

Three numbers carry the story. Adoption: about 76% of developers use or plan to use AI coding tools, so vibe coding is mainstream, not niche. Quality: GitClear’s analysis of hundreds of millions of changed lines found rising code churn and more duplicated code as AI adoption grew — speed traded against maintainability. Security: a Stanford study found developers using an AI assistant wrote less secure code while feeling more sure it was safe.

How big is the vibe coding market?

There’s no single dollar figure — but the adoption scale is the real answer: with roughly three in four developers now using AI coding tools, AI-assisted and fully AI-generated code has become the default way software gets built. Practically, that means a fast-growing share of the apps and side projects changing hands today were vibe-coded at least in part.

Common questionsFrequently asked questions

How many developers use AI coding tools?

A large majority. In Stack Overflow’s Developer Survey, roughly three in four developers were using or planning to use AI tools in their workflow, with a majority already using them regularly — making AI-assisted (and fully AI-generated, or 'vibe-coded') software mainstream rather than niche.

Is AI-generated code lower quality?

The research is mixed. AI tools clearly speed up writing code, but analyses like GitClear’s have found rising code churn and more duplicated, copy-pasted code alongside AI adoption — signals of lower maintainability. The takeaway isn’t 'AI code is bad'; it’s that AI-written code needs the same review, testing, and refactoring as any other code before it’s production-ready.

Are vibe-coded apps worth buying or selling?

Yes — a working, revenue-generating app is a real asset regardless of how it was built. But because AI-generated code varies in quality and security, buyers pay for proof: clean, reviewed code, tests, and no obvious vulnerabilities. Sellers who harden and document their build earn a higher price than those who ship a raw prototype.

What are the key vibe coding statistics for 2026?

Three numbers frame it. Adoption: roughly 76% of developers use or plan to use AI coding tools (Stack Overflow), so vibe coding is mainstream rather than niche. Quality: GitClear’s analysis of hundreds of millions of changed lines found rising code churn and more duplicated code as AI adoption grew — speed at the cost of maintainability. Security: a Stanford study found developers using an AI assistant wrote less secure code while feeling more confident it was safe.

How big is the vibe coding market?

There is no single dollar figure, but adoption tells the story: about 76% of developers now use or plan to use AI coding tools, and AI-assisted or fully AI-generated code has become the mainstream way software is built. That means a fast-growing share of the apps and side projects bought and sold today were vibe-coded at least in part.

Built it with AI?
Let the code prove it.

List your project free on Vertos — a built-in analysis shows buyers exactly what's under the hood, so a clean build earns its price. Keep 95%; flat 5% only when it sells.

List your project →

Ship fast — but review before you sell.
— The Vertos team

Sources & notes

Figures are drawn from public research and are directional; methodologies and yearly cohorts vary. Developer AI-tool adoption: Stack Overflow Developer Survey. Code quality, churn & duplication: GitClear. Security & developer over-confidence: Perry et al., Stanford (arXiv). This is general education, not security or investment advice.