A new study just debunked the biggest fear about AI and open source 近来有一项新研究，破除了坊间对于人工智能与开源社区联手时最大的忧虑。
There’s a common fear about what AI could do to open source. Coding agents take over the beginner-friendly issues that help new contributors get started; the code they generate is harder to maintain, and eventually, the pipeline of new maintainers dries up. It’s a plausible scenario. But according to new research, it doesn’t appear to be what’s actually happening. 江湖中流传着一种担忧：AI 恐将重塑开源格局。人们怕那些易于入门的任务被 AI 尽数揽去，新人便没了练手的机会；又怕 AI 生成的代码晦涩难懂，维护起来劳心劳力，长此以往，开源社区的新血恐将枯竭。这般推演，听来确有几分道理。然而依最新研究来看，事实却并非如此。
A study submitted to arxiv.org on July 2 out of Peking University tracked 1,888 GitHub repositories that adopted AI coding agents, tools like Cursor and Claude Code, to see how those projects changed after AI entered the workflow. The researchers treated adoption as the point when a project committed its first agent configuration file, something like a .cursorrules or CLAUDE.md, and then compared those projects against a matched set that never adopted.7 月 2 日，北京大学的研究团队在 arxiv.org 上发布了一份报告。他们追踪了 1,888 个引入 AI 编程助手（如 Cursor、Claude Code 等）的 GitHub 仓库，意在探究 AI 介入后，这些项目究竟发生了何种变化。研究员以项目提交首个代理配置文件（如 .cursorrules 或 CLAUDE.md）作为引入 AI 的分水岭，再将其与未引入 AI 的对照组进行比对。
They used difference-in-differences, which is basically the gold standard for separating what a tool actually caused from whatever was already going on in a project before the tool showed up. And what they found was…not much. Newcomer participation held steady or crept slightly upward. Under the most conservative statistical specification, the worst they could find was a 1.5% dip that didn’t approach statistical significance.他们采用了“双重差分法”，此乃甄别因果的利器，旨在剥离项目原有的演变趋势，精准锁定 AI 工具带来的实际影响。而所得结果却颇为平淡：新人参与度不仅未减，反而略有起色。即便在最严苛的统计模型下，最坏的情况也仅是出现了 1.5% 的微小波动，且并未达到统计学上的显著水平。
Complexity up, contributors steady代码愈发繁复，新人依旧如初
Cyclomatic complexity, which counts the number of independent paths through a function, ticked up 3% to 4% across all languages after adoption. Cognitive complexity, the trickier metric that penalizes heavily nested logic and tangled control flow, jumped by about 11% in Python projects. That sounds bad until you compare it to a Carnegie Mellon study published last year, which found that Cursor adoption drove a 41% increase in the same metric. The Peking University team, working with a larger and more established set of projects and tighter statistical controls, landed at roughly a quarter of that earlier estimate. 所谓“圈复杂度”（Cyclomatic complexity），即衡量函数中独立路径的数量。引入 AI 后，各语言项目的这一指标普遍上升了 3% 至 4%。而“认知复杂度”——这一衡量嵌套逻辑与控制流混乱程度的指标，在 Python 项目中更是激增了约 11%。乍看之下，这似乎是个坏消息，但若与卡内基梅隆大学去年的研究相比，便觉大不相同。彼时研究称 Cursor 导致了 41% 的增长。北大团队此次样本更广、底蕴更深，且统计控制更为严密，最终得出的数据仅为前者的四分之一。
But where the study really gets interesting is that instead of just reporting complexity and newcomer numbers as two separate findings that happen to live in the same PDF, they locked the analysis to the exact 128 Python projects where complexity actually increased. 此项研究的精妙之处，在于并未将复杂度与新人人数视为两份孤立的报表，而是将目光锁定在复杂度确实有所增长的 128 个 Python 项目上，进行了一番深究。
On those same repos, newcomer entry didn’t decline, retention held steady, and the active contributor base grew. Both effects are real, but they don’t seem to be connected. AI-generated code is getting a little more complicated, yet that extra complexity doesn’t appear to be discouraging newcomers, at least at the levels this study found. 在这些仓库中，新人并未减少，留存率稳如泰山，活跃贡献者群体反而有所壮大。看来，AI 带来的代码复杂化与新人流失之间，并无必然的因果关联。即便代码变得略微难解，也并未如众人所忧那般将新人拒之门外。
AI-generated code is getting a little more complicated, yet that extra complexity doesn’t appear to be discouraging newcomers, at least at the levels this study found.AI 生成的代码确实变得复杂了些，但依此项研究来看，这种复杂程度并未对新人造成阻碍。
What the study excluded研究的边界与局限
There are a few important caveats. The biggest issue is that the study focused on established open-source projects. Nearly two-thirds of the repositories that adopted AI coding tools did so almost as soon as they were created, leaving researchers with no meaningful pre-AI baseline for comparison. Those repositories were excluded from the main analysis, which instead focused on 603 projects with at least six months of history before AI was introduced. 当然，此项研究亦有几处需细细考量。其一，研究重心在于成熟的开源项目。近三分之二的仓库在创建之初便引入了 AI，导致研究者缺乏引入 AI 前的基准数据，故而这部分项目被排除在核心分析之外。最终参与比对的，是 603 个在引入 AI 前已有至少半年历史的项目。
The researchers also examined the full dataset, in which newcomer participation appeared to decline. But a closer look showed those projects were already losing contributors before they adopted AI, making it impossible to blame the decline on the tools themselves.研究者亦审视了全量数据集，其中新人参与度看似有所下滑。然而细察之下便知，这些项目在引入 AI 之前便已在流失贡献者，故而这笔账，终究不能全算在 AI 工具头上。
Measuring adoption’s blind spots衡量 AI 采纳的盲点
There’s another limitation, too. The study measures AI adoption by looking for configuration files associated with tools like Cursor, not by tracking how often developers actually used them. That means it can tell us what happened after projects adopted AI, but not whether teams that relied heavily on AI experienced different outcomes than teams that only experimented with it.此外，研究亦存局限。它通过配置文件来判定 AI 的引入，而非追踪开发者实际使用的频率。这意味着，它能告诉我们项目采纳 AI 后发生了什么，却无法分辨那些深度依赖 AI 的团队，与仅是浅尝辄止的团队，在结果上有何不同。
GitHub says merged pull requests across the platform have grown from about 25 million per month in early 2023 to roughly 90 million a month today. 据 GitHub 统计，平台上的合并拉取请求（PR）数量已从 2023 年初的每月约 2,500 万，激增至如今的每月约 9,000 万。
GitHub has started responding, too. The company recently introduced limits on the number of open pull requests that outside contributors can have at once, along with new tools to help maintainers sort through growing review queues.GitHub 亦已出招应对。公司近期限制了外部贡献者同时开启的 PR 数量，并推出了一系列新工具，助维护者从愈发繁重的审核队列中解脱出来。
The crowding-out fear is, for now, put to rest.“挤出效应”的忧虑，眼下暂可平息。
Where this leaves us何去何从
The crowding-out fear is, for now, put to rest. In established open-source projects, at current adoption levels, AI agents are not pushing newcomers out the door. However, pull request volume has nearly quadrupled. The code arriving in those PRs is a bit more complicated. The people submitting it may not fully grasp what they’re proposing. And all of that lands on maintainers whose ranks are not growing at anything like the same pace.“挤出效应”的忧虑，眼下暂可平息。在现有的开源生态中，AI 代理并未将新人拒之门外。然而，PR 的数量已近乎翻了四倍，代码亦愈发繁杂，提交者或许对所提方案亦非全盘通晓。这一切重担，最终皆落在了维护者肩上，而他们的队伍，却远未见有同等规模的壮大。
The researchers say future work should examine how heavily projects rely on AI coding tools and find better ways to study repositories that were effectively born with AI. Those are important next steps. But the question that feels most pressing is: Not whether AI changes who shows up to contribute, but whether it changes the effort required to maintain an open-source project over time.研究者指出，未来应深入探究项目对 AI 工具的依赖程度，并寻找更佳的路径来审视那些“伴随 AI 而生”的仓库。这些固然重要，但最紧迫的问题或许在于：AI 改变的并非谁来贡献，而是随着时日推移，维护一个开源项目所需的心力，是否已然变了。
Not whether AI changes who shows up to contribute, but whether it changes the effort required to maintain an open-source project over time.AI 改变的并非谁来贡献，而是随着时日推移，维护一个开源项目所需的心力，是否已然变了。
