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. 人们普遍担心人工智能可能对开源造成的影响。编码代理接管了那些帮助新贡献者起步的初学者友好型问题；它们生成的代码更难维护，最终，新维护者的来源枯竭。这是一个看似合理的场景。但根据新的研究，这似乎并非实际发生的情况。
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的北京大学研究追踪了1888个采用AI编码代理（如Cursor和Claude Code等工具）的GitHub仓库，以观察项目在AI进入工作流程后的变化。研究人员将采用定义为项目首次提交代理配置文件（如.cursorrules或CLAUDE.md）的时刻，然后将这些项目与一组从未采用此类工具的匹配项目进行比较。
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.他们使用了双重差分法，这基本上是区分工具实际造成的影响与项目原本趋势的黄金标准。而他们的发现是……变化不大。新参与者的参与度保持稳定或略有上升。在最保守的统计设定下，他们发现的最糟糕情况是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. 圈复杂度（衡量函数中独立路径的数量）在采用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. 但这项研究真正有趣之处在于，他们没有简单地将复杂度和新参与者人数作为同一份PDF中的两个独立发现来报告，而是将分析锁定在那些复杂度确实上升的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之前就已经在流失贡献者，因此无法将下降归咎于工具本身。
Measuring adoption’s blind spots衡量采用的盲点
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.还有另一个限制。该研究通过查找与Cursor等工具相关的配置文件来衡量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表示，平台上的合并拉取请求已从2023年初每月约2500万增长到如今每月约9000万。
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也已开始应对。该公司最近引入了限制，限制外部贡献者同时持有的开放拉取请求数量，并推出了新工具帮助维护者处理日益增长的审查队列。
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是否改变了前来贡献的人，而是它是否改变了长期维护一个开源项目所需的努力。
