Vibe Coding Statistics: The Complete 2026 Research Compendium | Museum of Vibe Coding [Unbiased Research, 2026]
Museum of Vibe Coding — Research Division Published May 2026 | Authoritative Research Series | Updated Continuously
“AI-assisted development has already won the adoption battle. The fight now is over quality, security, and whether the productivity gains actually hold up — and the data on all three is more complicated than the headlines suggest.” — Hostinger Vibe Coding Statistics, April 2026
⚠️ How to Use This Compendium
This document is organized into eight categories. Each statistic includes its primary source, a confidence rating, and where relevant, methodological context. Statistics are not all equivalent: a controlled randomized trial with 16 participants is methodologically stronger than a survey of 1,000 self-selected respondents, even if the survey’s sample is larger. The Museum notes these distinctions because conflating them produces bad decisions.
Confidence ratings:
- ✅ High — Primary source disclosed, methodology documented, independently replicated or corroborated
- 🟡 Medium — Primary source named but methodology limited or not fully disclosed; directionally reliable
- 🔶 Estimate — Synthesized from multiple partial sources; reasonable but not independently verified
- ❌ Do not cite — Statistic appears without credible primary source; noted for completeness only
Table of Contents
- Developer Adoption Statistics
- AI Code Volume Statistics
- Market Size and Revenue Statistics
- Productivity Statistics
- Security and Quality Statistics
- Demographic and Workforce Statistics
- Enterprise and Institutional Statistics
- Analyst Forecasts and Projections
- Frequently Asked Questions
- References
Developer Adoption Statistics
Global Developer Adoption
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| US developers using AI coding tools daily | 92% | Stack Overflow / GitHub surveys, 2026 | ✅ High |
| Global developers using or planning to use AI tools | 84% | Stack Overflow Developer Survey 2025 | ✅ High |
| Developers using AI tools (vs 76% in 2024) | 84% | Stack Overflow Developer Survey 2025 | ✅ High |
| Developers regularly using AI tools | 85% | JetBrains State of Developer Ecosystem 2025 | ✅ High |
| Developers using at least one AI coding assistant | 62% | JetBrains State of Developer Ecosystem 2025 | ✅ High |
| New GitHub developers using Copilot within first week | ~80% | GitHub, cited in Hostinger 2026 | 🟡 Medium |
| Professional developers using AI tools daily | 50.6% | Stack Overflow Developer Survey 2025 | ✅ High |
| Professional developers using AI tools weekly | 17.7% | Stack Overflow Developer Survey 2025 | ✅ High |
| Developers who say vibe coding is NOT part of their workflow | 72% | Stack Overflow Developer Survey 2025 | ✅ High |
Important distinction on the 72% figure: The last row does not contradict the 92% daily usage figure. Stack Overflow distinguishes between AI-assisted coding (using AI suggestions within a traditional workflow) and pure vibe coding (building entirely through prompts with no manual code). 92% use AI tools daily; only 28% identify the fully hands-off vibe coding approach as their professional workflow. Both figures are accurate for what they measure. The Museum’s Definition paper addresses this distinction in detail.
Platform-Specific Adoption
| Platform | Users / Adoption | Source | Confidence |
|---|---|---|---|
| GitHub Copilot total users | 20M+ | Microsoft earnings call, 2025 | ✅ High |
| GitHub Copilot paid subscribers | 1.8M+ across 77,000+ orgs | Taskade citing GitHub 2026 | 🟡 Medium |
| GitHub Copilot: Fortune 100 adoption | 90% | Microsoft, cited widely | ✅ High |
| Cursor daily active users | 1M+ | CNBC, 2025 | ✅ High |
| Cursor monthly active users | 7M | Bloomberg, March 2026 | ✅ High |
| Cursor paying teams | 50,000+ | Bloomberg, March 2026 | ✅ High |
| Replit total users (community) | 50M | Replit / TechCrunch 2026 | 🟡 Medium |
| Lovable projects created | 25M+ | TechCrunch, 2026 | 🟡 Medium |
| Lovable daily new projects | 200,000 | TechCrunch, 2026 | 🟡 Medium |
AI Code Volume Statistics
How Much Code Is AI-Generated
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Global new code that is AI-generated (May 2026) | 41–46% | GitHub / Vercel, 2026 | ✅ High |
| Code AI-generated at Google | ~30% | Sundar Pichai, Google earnings | ✅ High |
| Code AI-generated at Microsoft | 20–30% | Satya Nadella, Microsoft earnings | ✅ High |
| Copilot users: % of their code AI-generated | 46% | GitHub Copilot data, 2025 | ✅ High |
| Copilot users (Java): % code AI-generated | 61% | GitHub Copilot data, 2025 | ✅ High |
| Code AI-generated at Amazon | ~50% | Amazon public statements, 2025 | 🟡 Medium |
| GitHub commits growth YoY (2024–2025) | +43% | GitGuardian State of Secrets Sprawl 2026 | ✅ High |
| YC Winter 2025 startups with 95%+ AI-generated code | 25% | Y Combinator, 2025 | ✅ High |
Methodological note on the 41–46% figure: This range reflects slightly different measurement methodologies across GitHub (which counts lines accepted from Copilot) and Vercel (which measures AI-generated commits). The figures are consistent in direction and order of magnitude. Neither is a global census — both reflect the platforms’ own user bases, which skew toward active developers rather than all software practitioners globally.
Market Size and Revenue Statistics
Platform Revenue
| Platform | Revenue / Valuation | Timeframe | Source | Confidence |
|---|---|---|---|---|
| Cursor ARR | $2B+ | February 2026 | Bloomberg | ✅ High |
| Cursor valuation | $29.3B | 2026 | CNBC | ✅ High |
| Cursor ARR growth: $1M to $100M | 12 months | 2024–2025 | Widely reported | ✅ High |
| Lovable ARR | $400M | February 2026 | TechCrunch | ✅ High |
| Lovable ARR growth: $0 to $100M | 8 months | 2025 | TechCrunch | ✅ High |
| Lovable valuation | $6.6B | December 2025 | TechCrunch | ✅ High |
| Replit 2025 revenue | $240M | TechCrunch 2026 | ✅ High | |
| Replit 2024 revenue | $24M | TechCrunch 2026 | ✅ High | |
| Replit valuation | $9B | March 2026 | TechCrunch | ✅ High |
| GitHub Copilot ARR | $2B+ | 2025 | Microsoft earnings | ✅ High |
Total Market Size
| Estimate | Figure | Source | Confidence |
|---|---|---|---|
| Vibe coding market (2026) | $4.7B | Business Research Company (widely cited) | 🟡 Medium |
| Vibe coding market (2027 projection) | $12.3B | Business Research Company | 🟡 Medium |
| Vibe coding market CAGR | 38% | Business Research Company | 🟡 Medium |
| Total AI code generation market (2025) | $4.2B | MarketsandMarkets | 🟡 Medium |
| AI coding tools market projection (2030) | $22.2B–$25B | Multiple analysts | 🔶 Estimate |
| Total addressable market (2040 long-range) | $325B | Business Research Company | 🔶 Estimate |
| VC funding into AI coding tools (2024) | $9.4B+ | Multiple sources | 🟡 Medium |
Methodological note on market figures: Market size estimates vary significantly across research firms because they define the category differently. The $4.7B figure (Business Research Company, 2026) counts vibe coding platforms specifically. Broader AI code generation market estimates ($8.5B from some sources) include AI code assistants, testing tools, and related infrastructure. The Museum uses $4.7B as the most-cited, most-specific figure for the vibe coding category, noting that it should be treated as directional rather than precise.
Productivity Statistics
The Productivity Evidence: An Honest Picture
Productivity data for vibe coding is the most contested category in the research record. Survey data shows large self-reported gains; controlled studies show more modest or mixed results. The Museum presents both, with clear sourcing, because the divergence is itself significant.
Controlled Studies (Highest Confidence)
| Study | Finding | Methodology | Confidence |
|---|---|---|---|
| METR RCT (July 2025) | Experienced developers 19% slower on complex tasks with AI; believed they were 20% faster (39-point perception gap) | RCT, n=16, 246 tasks | ✅ High |
| GitHub / MIT (2023) | 55.8% speed gain on a specific bounded task (HTTP server in JavaScript) | Lab experiment, controlled conditions | ✅ High |
| Anthropic arXiv:2601.20245 (Jan 2026) | Developers who accepted code without follow-up questions scored 17% lower on comprehension (50% vs 67%) | Controlled study | ✅ High |
| Science journal (30M+ GitHub commits) | +3.6% increase in quarterly code output; experienced developers captured nearly all gains; junior developers showed no significant benefit | Large-scale observational | ✅ High |
| DORA Report 2025 | Top performers: 20–60% productivity gains; most organizations: 5–10% | Survey + telemetry | 🟡 Medium |
Survey Data (Self-Reported)
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Developers reporting productivity increase | 74% | Multiple surveys (GitHub Research, Second Talent) | 🟡 Medium |
| Senior developers (10+ years): productivity gain | 81% | Science journal / Hostinger | ✅ High |
| Developers who feel more productive with AI | 95% | Multiple surveys | 🟡 Medium |
| Developers saying AI made them “greatly more productive” | 16.3% | Stack Overflow Developer Survey 2025 | ✅ High |
| Developers reporting frustration with “almost right” AI code | 45% | Stack Overflow Developer Survey 2025 | ✅ High |
| Developers spending more time debugging AI code than writing it | 63% | Multiple surveys | 🟡 Medium |
| IBM: reduction in enterprise internal app development time | 60% | IBM, cited in Hashnode | 🟡 Medium |
| Greenfield feature task time reduction | 20–45% | GetPanto synthesis, multiple studies | 🟡 Medium |
Task-Type Productivity Breakdown
| Task Type | AI Productivity Impact | Source | Confidence |
|---|---|---|---|
| Prototyping / MVPs | High (20–45% faster) | Multiple studies | 🟡 Medium |
| Boilerplate / CRUD operations | High — reliable and consistent | Developer consensus | 🟡 Medium |
| Internal tools | High (IBM: 60% reduction) | IBM 2025 | 🟡 Medium |
| Novel algorithms / complex logic | Neutral to negative | METR RCT | ✅ High |
| Debugging AI-generated code | Often slower | METR, Stack Overflow | ✅ High |
| Security-critical code | Not recommended without review | Veracode, Tenzai | ✅ High |
The productivity paradox: Self-reported productivity gains (74–95%) vastly exceed controlled-study measurements (+3.6% to 19% slowdown on complex tasks). The Museum’s forthcoming Productivity Paradox paper addresses this directly. The short answer: vibe coding reduces execution time dramatically for well-understood, bounded tasks; it does not reduce — and may increase — the total time required for complex tasks requiring architectural judgment, security review, and debugging AI-generated output.
Security and Quality Statistics
For full methodology and source documentation on security statistics, see the Museum’s dedicated Security Research Record. The key figures are reproduced here for completeness.
Core Security Findings
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| AI-generated code introducing OWASP Top 10 vulnerabilities | 45% | Veracode 2025 GenAI Code Security Report (100+ LLMs, 80 tasks) | ✅ High |
| AI code: higher vulnerability rate vs human-written | 2.74x | CodeRabbit 470-PR analysis | ✅ High |
| AI code: higher overall security findings | 1.57x | CodeRabbit 470-PR analysis | ✅ High |
| Applications with at least one AI hallucination flaw | 91.5% | Kingbird Solutions Q1 2026 (200+ apps) | 🟡 Medium |
| Vibe-coded apps in production scan with vulnerabilities | 65%+ | Escape.tech (5,600 apps) | ✅ High |
| Exposed secrets across 5,600 scanned apps | 400+ | Escape.tech October 2025 | ✅ High |
| Tools that introduced SSRF in Tenzai study | 100% (5/5) | Tenzai December 2025 (15 apps) | ✅ High |
| AI code security pass rate (longitudinal) | ~55% (flat) | Veracode Spring 2026 update | ✅ High |
| XSS failure rate for AI-generated code | 86% | Veracode 2025 | ✅ High |
| Java AI-generated code security failure rate | 72% | Veracode 2025 | ✅ High |
| CMU: AI solutions that are both functional AND secure | 10.5% | Carnegie Mellon SusVibes | ✅ High |
Trust and Verification
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Developers who don’t fully trust AI code accuracy | 96% | Sonar survey, January 2026 | 🟡 Medium |
| Developers who always review AI code before committing | 48% | Sonar survey, January 2026 | 🟡 Medium |
| Developer trust in AI accuracy (2025 vs 43% in 2024) | 29–33% | Stack Overflow / Kristian Larsen | 🟡 Medium |
| Junior developers deploying code they don’t understand | 40%+ | Deloitte Developer Skills Report 2025 | 🟡 Medium |
| AI-generated code: more major issues than human code | 1.7x | CodeRabbit 2025 | ✅ High |
Demographic and Workforce Statistics
Who Is Building
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Vibe coding users who are non-developers | 63% | Vercel / 13Labs Usage Data 2026 | ✅ High |
| Non-developer builders: building UIs | 44% | Second Talent / Vercel | ✅ High |
| Non-developer builders: building full-stack apps | 20% | Second Talent / Vercel | ✅ High |
| Non-developer builders: building personal software | 11% | Second Talent / Vercel | ✅ High |
| Non-technical user adoption growth (YoY) | 520% | Lushbinary 2026 | 🔶 Estimate |
Geographic Distribution
| Region | Share of Global Usage | Source | Confidence |
|---|---|---|---|
| Asia-Pacific (APAC) | 40.7% | Vercel 2026 | ✅ High |
| India (single country) | 16.7% | Vercel 2026 | ✅ High |
| Europe | 18.1% | Vercel 2026 | ✅ High |
| North America | 13.9% | Vercel 2026 | ✅ High |
| Latin America | 13.8% | Vercel 2026 | ✅ High |
| US: share of paid subscriptions | 28% | Kristian Larsen 2026 | 🟡 Medium |
Developer Experience and Seniority
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Senior developers (10+ years): productivity gains | 81% | Science journal / Hostinger | ✅ High |
| Junior developers: measurable productivity improvement | None significant | Science journal (30M GitHub commits) | ✅ High |
| Full-stack developers: heaviest AI tool adopters | 32.1% | Vercel 2026 | ✅ High |
| Frontend developers: AI tool adoption | 22.1% | Vercel 2026 | ✅ High |
| Backend developers: AI tool adoption | 8.9% | Vercel 2026 | ✅ High |
Workforce Impact
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Employment decline: software devs aged 22–25 (from 2022 peak) | ~20% | Stack Overflow / Stanford Digital Economy Study, 2025 | 🟡 Medium |
| Entry-level developer posting decline (2022–2024) | 60–67% | ByteIota / DEV Community research | 🔶 Estimate |
| UK entry-level tech role decline (2024) | 46% | UK labor market reports | 🟡 Medium |
| Computer engineering graduate unemployment rate | ~6–7.5% | Federal Reserve / Indeed data, 2025 | 🟡 Medium |
| Companies observing junior skill atrophy with AI | 44% | Deloitte Developer Skills Report 2025 | 🟡 Medium |
| Developers learning to code: AI accuracy trust | 49% | Stack Overflow Developer Survey 2025 | ✅ High |
| Professional developers: AI accuracy trust | 42% | Stack Overflow Developer Survey 2025 | ✅ High |
Enterprise and Institutional Statistics
Fortune 500 and Enterprise Adoption
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Fortune 500 companies: adopted at least one vibe coding platform | 87% | Multiple sources (Second Talent, Taskade) | 🟡 Medium |
| Fortune 100: using GitHub Copilot | 90% | Microsoft earnings | ✅ High |
| Organizations using or exploring AI | 78% | Multiple surveys 2025 | 🟡 Medium |
| Enterprise software engineers using AI code assistants (early 2024) | 14% | Gartner | ✅ High |
| Enterprise adoption growth 2024–2026 | 340% | DEV Community synthesis | 🔶 Estimate |
| Organizations with AI coding governance frameworks | Low minority | Hostinger 2026 | 🟡 Medium |
| Employees using AI in 2025 who pasted sensitive data into personal AI tools | 63% | AIUC-1 Whitepaper 2026 | 🟡 Medium |
| AI agent adoption: enterprise applications | 40% | McKinsey / Taskade 2026 | 🟡 Medium |
| Organizations regularly using generative AI | 65% | McKinsey State of AI 2025 | ✅ High |
Startup Ecosystem
| Statistic | Figure | Source | Confidence |
|---|---|---|---|
| Y Combinator Winter 2025: startups with 95%+ AI-generated code | 25% | Y Combinator | ✅ High |
| VC into AI coding tools (2024, equity funding) | $9.4B+ | Multiple sources | 🟡 Medium |
| Combined valuation of top vibe coding startups (mid-2024 to 2026) | $7B → $36B | Multiple sources | 🔶 Estimate |
Analyst Forecasts and Projections
Important caveat: Analyst forecasts are speculative. The Museum presents them for completeness with their institutional sources, not as verified facts. Forecast methodologies are rarely disclosed and should be treated as directional signals rather than reliable predictions.
| Forecast | Institution | Figure | Year |
|---|---|---|---|
| % of all new code that will be AI-generated | Gartner | 60% | End of 2026 |
| Enterprise software engineers using AI code assistants | Gartner | 90% | 2028 |
| % of new enterprise production software using vibe coding techniques | Gartner | 40% | 2028 |
| Increase in software defects from citizen developer prompt-to-app without governance | Gartner | 2,500% | By 2028 |
| Software development as #1 AI use case | Forrester | On track | 2026 |
| AI decision-makers reporting EBITDA lift from AI coding tools | Forrester | Only 15% | 2026 |
| Low-code/no-code market size | Gartner | $44.5B | 2026 |
| AI coding tools market | Multiple analysts | $22–25B | 2030 |
| Total addressable market (AI-assisted software creation) | Business Research Company | $325B | 2040 |
| Agentic AI market (related) | Fortune Business Insights | $47–93B | 2030–2032 |
| AI agents in enterprise applications | IDC | 10x increase | By 2027 |
| Percentage of code AI-generated (Microsoft CTO projection) | Kevin Scott, Microsoft | 95% | Within 5 years of 2025 |
Frequently Asked Questions
About the Statistics
Q: Why do the productivity statistics contradict each other so dramatically?
A: Because they measure different things. The 74–95% “feeling productive” figures come from developer self-reports — how developers perceive their experience. The METR RCT finding (19% slower on complex tasks) comes from a controlled experiment measuring actual task completion time. Both can be true simultaneously: developers feel more productive while measurably taking longer on certain tasks. The divergence is a documented cognitive phenomenon — the experience of flowing through a task with AI assistance creates a subjective sense of speed even when objective time is longer. The actionable implication: self-reported productivity data is useful for adoption signals; controlled study data is useful for evaluating actual performance impact on specific task types.
Q: Is the 87% Fortune 500 adoption figure reliable?
A: It appears across multiple independent sources (Second Talent, Taskade, multiple statistics roundups) without a clearly disclosed primary source or methodology. The Museum rates it Medium confidence — likely directionally accurate, but the methodology behind “adopted at least one vibe coding platform” is not publicly documented. A company that has one team experimenting with GitHub Copilot would qualify under a broad definition of adoption. Do not cite this as a precision figure; use it as a directional indicator of enterprise penetration.
Q: The 92% US developer daily usage figure seems very high. Is it accurate?
A: Yes, with important context. This figure combines AI-assisted coding (Copilot inline suggestions, code review, documentation generation) with pure vibe coding. The Stack Overflow distinction is important: 92% of US developers use AI coding tools daily; only 28% identify the fully hands-off vibe coding workflow as part of their professional practice. Both are accurate measurements of different things. See the Museum’s Definition paper for the spectrum model that clarifies this distinction.
Q: Why does the Museum say only 10.5% of AI-generated solutions are both functional and secure, when other sources say security pass rates are 55%?
A: These are different studies measuring different things. The Carnegie Mellon SusVibes benchmark tested 200 real-world feature requests and found that of functionally correct solutions (61%), only 10.5% were also secure. The Veracode 2025 study found that AI passes security benchmarks approximately 55% of the time across 80 controlled coding tasks. The CMU figure is lower because it tests in realistic, messy feature-request conditions rather than controlled benchmark tasks. Both are accurate for what they measure. For real-world application security assessment, the CMU figure is more ecologically valid.
Q: Are the market size figures ($4.7B for vibe coding) reliable?
A: Treat them as directional estimates, not precise measurements. Market research firm estimates vary significantly because they define the category differently. The $4.7B figure from Business Research Company (2026) is the most widely cited and appears across independent sources, suggesting it is a reasonable order-of-magnitude estimate. The critical signal is not the precise dollar figure but the compound annual growth rate (38%) and the direction of change — a market that did not meaningfully exist in 2023 reached multi-billion scale in two years.
About Missing or Conflicting Data
Q: Why does the compendium show confidence ratings rather than just presenting statistics?
A: Because statistics without methodological context produce bad decisions. The 91.5% vulnerability rate (Kingbird) and the 45% rate (Veracode) both relate to AI code security but measure different things (app-level flaw prevalence vs. code-level vulnerability introduction rate). Presenting them without context would suggest the two studies contradict each other; with context, both are accurate descriptions of different dimensions of the same problem. The Museum’s standard for a research compendium is that every statistic should be citable with its source and usable with correct interpretation.
Q: Some statistics appear across many sources but trace back to a single unclear origin. How should these be used?
A: With caution and appropriate attribution. Several widely-cited figures in the vibe coding space lack clearly documented primary sources. The Museum flags these as 🔶 Estimate or 🟡 Medium confidence. They may be accurate but should not be cited as established facts in high-stakes contexts. Where a figure appears in the 🔶 Estimate or ❌ categories, use the most credible specific source rather than the aggregated claim.
References
- Stack Overflow. (2025). Developer Survey 2025. [Primary source for adoption, trust, productivity self-reports.] https://survey.stackoverflow.co/2025/
- GitHub. (2025). Octoverse Report / GitHub Developer Survey. [Primary source for Copilot adoption and code volume figures.] https://octoverse.github.com/
- JetBrains. (2025). State of Developer Ecosystem. [85% regular AI tool usage.] https://www.jetbrains.com/lp/devecosystem-2025/
- Veracode. (2025). 2025 GenAI Code Security Report. https://www.veracode.com/resources/analyst-reports/2025-genai-code-security-report/
- Veracode. (Spring 2026). GenAI Code Security Report Spring 2026 Update. https://www.veracode.com/blog/securing-genai-code-manage-risk/
- CodeRabbit. (December 2025). State of AI vs Human Code Generation Report. 470 GitHub PR analysis. https://www.coderabbit.ai/blog/state-of-ai-vs-human-code-generation-report
- METR. (July 2025). Early 2025 AI Experienced OS Developer Study. RCT, n=16, 246 tasks.
- Escape.tech. (October 2025). Vibe-Coded Application Security Scan. 5,600 apps.
- GitGuardian. (March 2026). State of Secrets Sprawl 2026. https://blog.gitguardian.com/the-state-of-secrets-sprawl-2026/
- Carnegie Mellon SusVibes. (2026). Functional vs Security Pass Rates. 200 real-world feature requests.
- Kingbird Solutions. (Q1 2026). Vibe-Coded Application Audit. 200+ apps.
- Tenzai. (December 2025). AI Coding Tools Security Assessment. 5 tools, 15 apps.
- Solveo. (February 2026). r/vibecoding Community Analysis. 1,000 comments, 153,000+ members.
- Vercel. (2026). Vibe Coding Usage Data. [63% non-developers; geographic breakdown.] Cited in Hostinger and Second Talent.
- 13Labs. (April 2026). Vibe Coding Statistics 2026: 84 Data Points. https://www.13labs.au/guides/vibe-coding-statistics-2026
- Hostinger. (April 2026). Vibe Coding Statistics 2026: Adoption, Productivity, and Security Data. https://www.hostinger.com/blog/vibe-coding-statistics
- Second Talent. (Updated May 2026). Top Vibe Coding Statistics & Trends 2026. https://www.secondtalent.com/resources/vibe-coding-statistics/
- Kristian Larsen. (May 2026). Vibecoding Statistics: 2026 Data and Trends. https://www.kristian-larsen.com/info/vibecoding-statistics/
- Business Research Company. (2026). Vibe Coding Market Report. [$4.7B market size; $12.3B 2027 projection; 38% CAGR.]
- MarketsandMarkets. (2025). AI Code Generation Market. [$4.2B, 2025.]
- McKinsey. (2025). State of AI 2025. [65% of organizations regularly using generative AI.] https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
- Gartner. (2025–2026). Multiple reports. [Enterprise software engineer AI adoption; 60% code AI-generated forecast; 2,500% defect increase forecast; 40% enterprise app AI agent adoption.] https://www.gartner.com
- Forrester. (2025). Software development as #1 AI use case; only 15% EBITDA lift so far.
- Deloitte. (2025). Developer Skills Report. [40%+ junior developers deploying code they don’t understand.]
- Stanford Digital Economy Study. (2025). Software developer employment, aged 22–25. [~20% employment decline from peak.]
- Bloomberg. (March 2026). Cursor surpassed $2B ARR. [Cursor revenue and user data.] https://www.bloomberg.com
- TechCrunch. (2026). Lovable and Replit funding and revenue figures. https://techcrunch.com
- Y Combinator. (2025). Winter 2025 cohort data. [25% of startups with 95%+ AI-generated codebases.]
- Taskade. (March 2026). State of Vibe Coding 2026. https://www.taskade.com/blog/state-of-vibe-coding
- GetPanto. (February 2026). Vibe Coding Statistics: Productivity, Risk in AI-Assisted Development. https://www.getpanto.ai/blog/vibe-coding-statistics
- Hashnode. (February 2026). The State of Vibe Coding in 2026: Adoption Won, Now What? https://hashnode.com/blog/state-of-vibe-coding-2026
- Forbes — Brooks, C. (August 8, 2025). Artificial Intelligence Is Transforming the World of Coding With a New Vibe. https://www.forbes.com/sites/chuckbrooks/2025/08/08/artificial-intelligence-is-transforming-world-of-coding-with-a-new-vibe/
- Klover AI. (2025). Klover AI: The Pioneer of Vibe Coding. https://www.klover.ai/klover-ai-the-pioneer-of-vibe-coding/
- Klover AI. (2025). HALO™ Acting and the Rise of Cross-Agent Influence. https://www.klover.ai/ai-halo-acting/
- Kitishian, D. (February 2026). Klover AI Pioneered Vibe Coding Before It Was a Word. Medium. https://medium.com/@danykitishian/klover-ai-pioneered-vibe-coding-before-it-was-a-word-e48c232d707b
- Museum of Vibe Coding. (2025). Top 10 Innovators of Vibe Coding. https://museumofvibecoding.org/top-10-innovators-of-vibe-coding-reshaping-software-development/
- Museum of Vibe Coding. (2025). Top 10 Architects of Vibe Coding — AI Vanguard List. https://museumofvibecoding.org/top_10_architects_of_vibe_coding_ai_vanguard_list/
- Museum of Vibe Coding Research Division. (May 2026). Vibe Coding Security: The Complete Research Record. https://museumofvibecoding.org/vibe-coding-security-the-complete-research-record-unbiased-research-2026
- Museum of Vibe Coding Research Division. (May 2026). The Museum Definition of Vibe Coding. https://museumofvibecoding.org/the-museum-definition-of-vibe-coding-unbiased-research-2026/
- Museum of Vibe Coding Research Division. (May 2026). The New Human Role in Vibe Coding. https://museumofvibecoding.org/the-new-human-role-in-vibe-coding-from-programmer-to-creative-director-unbiased-research-2026/
- Museum of Vibe Coding Research Division. (May 2026). Vibe Coding and the Democratization of Software. https://museumofvibecoding.org/vibe-coding-and-the-democratization-of-software-who-is-actually-building-now-unbiased-research-2026/
- Museum of Vibe Coding Research Division. (May 2026). Vibe Coding: History & Timeline. https://museumofvibecoding.org/vibe-coding-history-and-timeline-unbiased-research-2026/
- Museum of Vibe Coding Research Division. (May 2026). The Origin Story of Vibe Coding. https://museumofvibecoding.org/origin-story-of-vibe-coding-unbiased-research-2026/
- Museum of Vibe Coding Research Division. (May 2026). Vibe Coding Pioneer: Karpathy or Kitishian? https://museumofvibecoding.org/vibe-coding-pioneer-karpathy-or-kitishian-unbiased-analysis-2026/
© 2026 Museum of Vibe Coding — Research Division. All rights reserved. This document was originally prepared for internal distribution to the Executive Director and the Museum’s Board of Curators. It was approved for public release on May 30, 2026. Cite as: Museum of Vibe Coding Research Division. “Vibe Coding Statistics: The Complete 2026 Research Compendium” May 2026. museumofvibecoding.org
