AI saves coding time—but who absorbs the review work?
A Linux Foundation survey of 234 open-source contributors and maintainers reports a 52% average self-estimated reduction in code-authoring time. Maintainers also estimated that one in four incoming pull requests was low quality.
The short version
- What happened
- Among 234 qualified respondents, contributors self-estimated an average 52% reduction in code-authoring time when using generative AI.
- Who it affects
- Volunteer maintainers may absorb more triage and review work when AI makes it easier to submit plausible but weak patches.
- What remains unproven
- The study uses a self-selected web survey rather than repository telemetry or a controlled comparison.
Faster authoring does not remove the verification work
Open-source contributors using generative AI estimated that it cut their code-authoring time by 52% on average, according to a Linux Foundation Research survey published on 20 October. Yet maintainers answering a separate question estimated that 25% of incoming pull requests were low quality. In projects with more than 50 contributors, that estimate rose to 31%. The pairing matters: time saved while drafting code can reappear as review, testing and explanation work for someone else.[1]
The survey reached 234 people, with smaller denominators for individual questions
Researchers fielded a 45-question web survey from April to June 2026 and retained 234 qualified responses. The sample included 206 contributors and 134 maintainers, with roles overlapping. Participants were recruited through Linux Foundation newsletters and social channels, plus communities connected to Red Hat, OpenSSF, Kaiyuanshe, GOSIM and LF AI & Data. The report gives the full sample a margin of error of plus or minus 6.41 percentage points at 95% confidence.[1]
Who it affects
Volunteer maintainers may absorb more triage and review work when AI makes it easier to submit plausible but weak patches.[1]
Keep in mind
The study uses a self-selected web survey rather than repository telemetry or a controlled comparison.
Key questions have smaller denominators than the 234-person full sample, increasing uncertainty for subgroup estimates.
Reported time savings and pull-request quality are participant estimates and do not measure downstream defects or maintenance cost.
The work was sponsored by Red Hat and supported by organisations active in open source and AI governance.
Source analysis · 1 linked source. Original source date: 20 October 2026.
Keep following the evidence
Join The Impact Brief founding list for selected AI reports, their effect on people and the evidence limits. Read a sample first.
Read the full report · 4 min The evidence, methods, implications and limitations
Faster authoring does not remove the verification work
Open-source contributors using generative AI estimated that it cut their code-authoring time by 52% on average, according to a Linux Foundation Research survey published on 20 October. Yet maintainers answering a separate question estimated that 25% of incoming pull requests were low quality. In projects with more than 50 contributors, that estimate rose to 31%. The pairing matters: time saved while drafting code can reappear as review, testing and explanation work for someone else.
The report also says 59% of maintainers saw contribution volume growing. More participation can strengthen a project, but maintainers must decide whether a change is correct, secure, licensed appropriately and consistent with project conventions. Generative AI may lower the effort needed to propose a patch without lowering the expertise needed to accept it or document why it was rejected for another contributor. The survey therefore points to a redistribution of work, not simply a universal productivity gain.[1]
The survey reached 234 people, with smaller denominators for individual questions
Researchers fielded a 45-question web survey from April to June 2026 and retained 234 qualified responses. The sample included 206 contributors and 134 maintainers, with roles overlapping. Participants were recruited through Linux Foundation newsletters and social channels, plus communities connected to Red Hat, OpenSSF, Kaiyuanshe, GOSIM and LF AI & Data. The report gives the full sample a margin of error of plus or minus 6.41 percentage points at 95% confidence.
Individual results often use smaller bases. The low-quality pull-request estimate came from 111 maintainers, so its uncertainty is wider than the full-sample figure. The 52% authoring-time result is a respondent estimate rather than observed elapsed time. Respondents were self-selected and already engaged with open source, which limits generalisation to all developers, companies or projects. The study is cross-sectional and cannot show that AI caused the reported changes.[1]
The distinction that matters
Where an apparent coding-time gain can move
The survey separates authoring from the downstream work needed before code becomes dependable.
Draft
AI assists code authoring
Respondents report time saved
Review
Maintainers inspect and test
Quality burden may shift
Operate
Projects maintain accepted code
Long-term cost remains unmeasured
Teams need review capacity, disclosure rules and evidence from actual repositories
Governance is uneven. Thirty-five per cent of respondents said their organisation had a formal policy permitting generative AI, while 32% reported no policy and no plans for one. Sixty-one per cent of contributors said they performed detailed review and full testing of AI-assisted contributions. Those answers suggest that conscientious practice exists, but they do not reveal whether the checks consistently catch security, licensing or maintenance problems.
For maintainers, the practical response is to make contribution expectations explicit, automate routine checks where appropriate and budget human attention for complex review. Employers adopting AI coding tools should measure the whole workflow: authoring time, review time, rework, defects, security findings and long-term maintenance. They should also distinguish a patch that is rejected quickly from one whose hidden defects emerge after release. The report was sponsored by Red Hat, with support from Futurewei, OpenSSF and LF AI & Data. Stronger evidence would link disclosed AI use to repository telemetry and compare matched projects over time.[1]
Watch the background, then check the evidence
Illustrative photo · not a video frame
UNESCO · 11 min 27 sec · Background explainer
UNESCO Talks: Interview with 2024 Nobel laureate Professor Daron Acemoglu
YouTube loads only when you choose; playback starts when you press play.
Economist Daron Acemoglu discusses how choices about AI affect workers, inequality and society. Pair the interview with our comparison of task exposure, hiring and skills evidence.
Evidence check: An expert interview from 2024, offering a perspective on policy and work rather than a measured forecast of job losses.
Published 2024-10-14. Source checked 14 October 2026. Check captions on the publisher’s video page.
Read the AI and jobs guidePhoto: Dylan Gillis / Unsplash · Licence
Evidence check
The study uses a self-selected web survey rather than repository telemetry or a controlled comparison.
Key questions have smaller denominators than the 234-person full sample, increasing uncertainty for subgroup estimates.
Reported time savings and pull-request quality are participant estimates and do not measure downstream defects or maintenance cost.
The work was sponsored by Red Hat and supported by organisations active in open source and AI governance.
Reporting basis: Source analysis. Original source date: 20 October 2026.
Continue the story
Read next
Continue exploring code review: compare the finding and its evidence limits.
Does an AI label bias code review—or does job rank matter more?
In a randomized vignette experiment, 447 Microsoft engineers did not penalize an AI-use disclosure on identical code, but rated the same code and author more favourably when the fictional author was labelled Principal rather than Level 1. One AI-normalized US workplace cannot settle how other teams respond.
Read the next reportExplore the full source and evidence record
What this means for people
- Volunteer maintainers may absorb more triage and review work when AI makes it easier to submit plausible but weak patches.
- Contributors benefit from faster drafting only if they remain accountable for testing, disclosure and responding to review.
Global context
Open-source projects often rely on volunteer or thinly funded maintenance across borders. A tool that expands participation can still create a bottleneck if review labour, project rules and testing infrastructure do not grow with submission volume.
What the evidence does not yet show
- The study uses a self-selected web survey rather than repository telemetry or a controlled comparison.
- Key questions have smaller denominators than the 234-person full sample, increasing uncertainty for subgroup estimates.
- Reported time savings and pull-request quality are participant estimates and do not measure downstream defects or maintenance cost.
- The work was sponsored by Red Hat and supported by organisations active in open source and AI governance.
What to watch next
- Repository-level studies comparing AI-disclosed and other pull requests on review time, defects and acceptance
- Whether projects adopt contribution policies that require disclosure, testing and author accountability
- Evidence about long-term maintenance, security and licensing outcomes rather than drafting speed alone
Living evidence record
Impact record IAI-0KH92KY
Evidence stage
Observed
Confidence
Supported
Reporting basis
Source analysis
Independent or research support
Not yet
Record status
Monitoring
Last checked
20 October 2026
Source trail
1 direct source across 1 source type.
People impact
Documented in this record.
Uncertainty
Limits and next checks are explicit.
Stages describe the evidence available—not whether a technology is good or bad. See the public method.
Single-source reporting disclosure
This record analyses one direct source. It can establish what Linux Foundation Research published or reported, but it is not independent corroboration of every performance claim or predicted outcome. The confidence label will change only when broader evidence is added.
Evidence trail
Sources used for this report
Links checked 20 October 2026
Research question, topics and regions
What a 2026 Linux Foundation survey indicates about generative AI productivity, pull-request quality and maintainer workload
Topics: Software work · Open source · Code review · Maintainers · Generative AI
Regions: Global · Open-source communities
This report is labelled source analysis. We summarise and analyse source material in our own words; company statements remain attributed claims until independently supported. Translated summaries preserve the meaning of the original source and link back to it. Read our editorial standards.
Reader commentary
What does this mean where you are?
Tell us what you have seen at work, in your community or in everyday life. A question is welcome too. No account is needed; we review notes before publishing them.
Explore commentary across the portal →Published reader notes
0No published reader notes yet. You can start the evidence-led discussion above.
Prefer a private correction or response? Contact the newsroom.