Debt Behind the AI Boom: A Large-Scale Empirical Study of AI-Generated Code in the Wild
Not on the map. Why?
Abstract (arXiv)
AI coding assistants are now widely used in software development. Software developers increasingly integrate AI-generated code into their codebases to improve productivity. Prior studies have shown that AI-generated code may contain code quality issues under controlled settings. However, we still know little about the real-world impact of AI-generated code on software quality and maintenance after it is introduced into production repositories. In other words, it remains unclear whether such issues are quickly fixed or persist and accumulate over time as technical debt. In this paper, we conduct a large-scale empirical study on the technical debt introduced by AI coding assistants in the wild. To achieve that, we built a dataset of 302.6k verified AI-authored commits from 6,299 GitHub repositories, covering five widely used AI coding assistants. For each commit, we run static analysis before and after the change to precisely attribute which code smells, correctness issues, and security issues the AI introduced. We then track each introduced issue from the introducing commit to the latest repository revision to study its lifecycle. Our results show that we identified 484,366 distinct issues, and that code smells are by far the most common type, accounting for 89.3% of all issues. We also find that more than 15% of commits from every AI coding assistant introduce at least one issue, although the rates vary across tools. More importantly, 22.7% of tracked AI-introduced issues still survive at the latest version of the repository. These findings show that AI-generated code can introduce long-term maintenance costs into real software projects and highlight the need for stronger quality assurance in AI-assisted development.
Key facts. Cited by 9 papers in the map (data through 7 Oct 2026). First posted on arXiv 30 Mar 2026.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2026: 9.
9 papers.
- 2026Dive into Claude Code: The Design Space of Today's and Future AI Agent Systemscited by 33
- 2026Is Agent Code Less Maintainable Than Human Code?cited by 1
- 2026The Substrate Collapse: AI Code Generation Invalidates Authorship-Based Knowledge Metricscited by 0
- 2026Augmentation with Dilution: A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoptioncited by 0
- 2026Do These Violent Delights Have Violent Ends? Measuring the Post-Merge Fate of Agentic Codecited by 0
- 2026Super Library Agent: Joint Generation and Maintenance of Multiple Applications Beyond the Single Codebasecited by 0
- 2026What is the Difference Between Me and You? Benchmarking the Quality Gap Between Human-Written and AI-Generated Codecited by 0
- 2026Who Finishes the Job? A Study of Follow-Up Fixes and Commit Authorship on AI Coding Agent Pull Requestscited by 0
- 2026Between the Commits: Process, Error, and Claim Reliability in a Wholly AI-Authored Codebasecited by 0
- 2026Between the Commits: Process, Error, and Claim Reliability in a Wholly AI-Authored Codebase24 Sep 2026
- 2026Who Finishes the Job? A Study of Follow-Up Fixes and Commit Authorship on AI Coding Agent Pull Requests22 Sep 2026
- 2026What is the Difference Between Me and You? Benchmarking the Quality Gap Between Human-Written and AI-Generated Code11 Sep 2026
- 2026Super Library Agent: Joint Generation and Maintenance of Multiple Applications Beyond the Single Codebase29 Aug 2026
- 2026Do These Violent Delights Have Violent Ends? Measuring the Post-Merge Fate of Agentic Code10 Jul 2026
- 2026Augmentation with Dilution: A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption24 Jun 2026
- 2026Is Agent Code Less Maintainable Than Human Code?19 Jun 2026
- 2026The Substrate Collapse: AI Code Generation Invalidates Authorship-Based Knowledge Metrics18 Jun 2026
- 2026Dive into Claude Code: The Design Space of Today's and Future AI Agent Systems14 Apr 2026