Editorial Standards

Last Updated: August 7, 2026

Vibecodingstats.dev exists to make data on AI-assisted coding, developer adoption, and the vibe coding economy easier to understand, verify, and cite. Every statistic we publish follows consistent editorial standards designed to prioritize accuracy over speed.

Our reporting is independent, evidence-based, and updated as the industry evolves.

Accuracy Comes First

Vibe coding is a fast-moving category where numbers can shift dramatically between quarters. Every statistic on this site is checked against its original source whenever possible.

Before publication, we verify:

  • Numerical accuracy
  • Publication date of the underlying research
  • Source credibility
  • Context in which the figure was reported
  • Units, definitions, and methodology
  • Whether the figure refers to “vibe coding” (prompt-to-app) or the broader “AI-assisted coding” category

We do not publish statistics that cannot be independently verified against a traceable source.

We Prioritize Primary Sources

Our preferred sources include:

  • Developer surveys (Stack Overflow, Vercel, GitHub Octoverse)
  • Platform disclosures and earnings reports (GitHub, Anthropic, Cursor, Lovable, Replit)
  • Academic and independent research (METR, Stanford, Georgia Tech, ACM studies)
  • Enterprise research firms (McKinsey, Gartner, Forrester)
  • Security research (Veracode, CodeRabbit, OWASP, Escape.tech, OX Security)
  • Regulatory and government publications
  • Verified investor and funding reports

Secondary sources such as industry aggregators or news coverage are used only when the original publication is unavailable or paywalled, and are labeled accordingly.

Context Matters

Numbers without context can be misleading, and this is especially true for vibe coding, where self-reported productivity often diverges sharply from measured productivity.

Whenever possible, we explain:

  • What the statistic actually measures
  • Who conducted the research
  • Sample size and participant profile
  • Time period covered
  • Geographic and industry scope
  • Whether the figure is self-reported, observed, or projected
  • Important limitations or known biases

Where reported and measured figures conflict, such as the METR study showing developers felt 20% faster but were 19% slower, we present both rather than choosing the more flattering number.

Distinguishing Categories

Industry reporting frequently conflates two distinct markets:

  • AI-assisted coding: professional developer tools such as GitHub Copilot, Cursor, and Claude Code
  • Vibe coding / prompt-to-app: platforms such as Lovable, Replit, Bolt.new, and Base44 aimed at both developers and non-technical builders

We note the distinction wherever it materially affects the interpretation of a statistic, particularly for market size, adoption, and user demographic figures.

Independence

Our editorial decisions are never influenced by advertisers, sponsors, platforms we cover, or affiliate relationships.

If a page contains affiliate links or sponsored content, it is clearly disclosed at the top of the page.

Commercial relationships do not affect:

  • Which statistics we publish
  • Which platforms or studies we cover
  • How we interpret research findings
  • Our editorial conclusions or rankings

Platform valuations, ARR figures, and funding milestones are reported as disclosed by the companies or their investors. Where figures are estimated by third parties rather than confirmed, we label them as estimates.

Corrections Policy

Accuracy is an ongoing process, particularly in a market where quarterly ARR figures and adoption numbers can move by billions.

If we discover an error, we:

  • Review the original source
  • Verify the correction against additional sources where possible
  • Update the article promptly
  • Note significant corrections at the bottom of the affected page
  • Revise outdated statistics when newer data becomes available

Readers are encouraged to report suspected errors, broken source links, or updated figures through our Contact page.

AI-Assisted Writing

Given the subject of this site, it would be dishonest not to disclose our own use of AI. We may use AI tools to assist with research organization, drafting, summarization, and editing.

However:

  • Every statistic is verified by a human editor against its original source
  • Every citation is manually reviewed
  • AI is never treated as a source of factual information
  • AI-generated figures, projections, or summaries are never published as data
  • Final editorial decisions are made by our research team

Content Updates

Vibe coding is one of the fastest-moving categories in software. Adoption rates, platform revenues, valuations, and security findings can change in weeks.

Instead of publishing pages once and leaving them unchanged, we routinely review existing reports to:

  • Add new statistics as fresh research is published
  • Remove or flag outdated figures
  • Replace broken or moved source links
  • Update platform ARR, valuation, and user counts
  • Improve explanations and context
  • Expand coverage into new subtopics such as agentic engineering, governance, and security tooling

Each page displays its last updated date so readers can judge the recency of the data.

Our Commitment

We believe trustworthy statistics should be:

  • Accurate
  • Transparent about methodology and limitations
  • Properly sourced to primary research
  • Easy to verify
  • Easy to cite
  • Updated regularly as the industry changes

Those principles guide every page we publish.

For corrections, data submissions, or research partnerships, contact the editorial team at vibecodingstats.dev.

Scroll to Top