AI can speed up coding and surface bugs, but maintainers still have to verify the results. A Linux Foundation survey found 25% of incoming pull requests were considered low quality, rising to 31% at large projects.
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: How is AI accelerating open-source development while overwhelming maintainers with low-quality contributions and vulnerability reports, as i. Article summary: AI is making code and potential bug reports faster to produce, but that does not make them faster to validate: the bottleneck is shifting toward maintainers’ review and security judgment. OpenSSL’s report surge and the L. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
AI is making it easier to produce code and identify potential bugs. But each contribution or security report still needs review—and that work can become the bottleneck. OpenSSL’s growing report volume and a Linux Foundation survey of open-source contributors show both sides of the trade-off: faster development, but more material for maintainers to assess. 1
21
OpenSSL provides software used to secure internet communications, making the quality and security of its code important well beyond the project itself. 1
5
At the project’s annual conference in Prague, executive director Matt Caswell said OpenSSL received an average of 71 security reports and inquiries per month from May through July 2026, compared with nine per month during the same period a year earlier. The total reached 108 inquiries in August. 1
Those figures describe incoming reports and inquiries—not confirmed vulnerabilities. Over the preceding year, OpenSSL received roughly 500 vulnerability reports, but 63 resulted in disclosed vulnerabilities. Many submissions were duplicates, minor defects, or issues that did not warrant a security advisory. Most vulnerabilities found with AI tools were low severity, rather than major security flaws. Even so, submissions take human effort to assess. 1
3
The added review pressure is not unique to OpenSSL. Maintainers from Bouncy Castle and cryptlib also described having more reports to examine at the conference. Bouncy Castle’s Megan Woods warned about the risks of AI-authored cryptographic code, reinforcing the need to treat generated code with care. 2
3
AI tools can help with tasks such as reviewing code, investigating reported vulnerabilities, and writing tests, according to OpenSSL’s chief technology officer. 3 These uses may support maintainers’ work, but they do not make a potential finding a confirmed flaw or remove the need for human assessment.
1
3
That distinction matters because discovery and verification are different jobs. A tool can surface a suspicious code path or produce a plausible report; maintainers still need to determine whether it describes a real, relevant issue and what to do about it. The conference reporting says investigations, patch development, and security-advisory publication can take six to eight weeks. 3
A Red Hat-sponsored Linux Foundation Research survey, presented at All Things Open, found that maintainers estimated 25% of incoming pull requests were low-quality “AI slop.” The share rose to 31% at large projects. The survey covered 234 open-source contributors and maintainers. 20
21
At the same time, 59% of project maintainers reported an increase in contributions. 21 More submissions can bring useful work and new contributors, but the volume also adds review demands—particularly when contributions arrive with problems that maintainers must identify and explain.
The findings are survey estimates, not a count of every pull request across open-source projects. They nevertheless point to a practical challenge: AI can reduce the effort involved in producing a contribution without reducing the effort required to decide whether it is ready to merge. 20
21
Google’s response shows how increased intake can affect security-reporting programs. On October 1, it paused new product-vulnerability submissions to its Open Source Software Vulnerability Reward Program, citing a rise in automated submissions, the vast majority of which it said were invalid. Google said it would provide an update in the first quarter of 2027. The pause applied to product-vulnerability submissions to that program, not every Google vulnerability-reward program. 18
For open-source projects, the evidence points to a balanced approach: make contribution expectations clear, ask for reproducible evidence and tests where relevant, and use automation to help triage—not to bypass human review. Those are practical implications of the reporting, rather than a single prescribed solution. 1
18
21
AI can make it faster to write code and find potential defects. Trustworthy software still depends on maintainers having the time and support to check what arrives.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
AI can speed up coding and surface bugs, but maintainers still have to verify the results.
AI can speed up coding and surface bugs, but maintainers still have to verify the results. A Linux Foundation survey found 25% of incoming pull requests were considered low quality, rising to 31% at large projects.
AI can speed up coding and surface bugs, but maintainers still have to verify the results. A Linux Foundation survey found 25% of incoming pull requests were considered low quality, rising to 31% at large projects.
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: How is AI accelerating open-source development while overwhelming maintainers with low-quality contributions and vulnerability reports, as i. Article summary: AI is making code and potential bug reports faster to produce, but that does not make them faster to validate: the bottleneck is shifting toward maintainers’ review and security judgment. OpenSSL’s report surge and the L. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
AI is making it easier to produce code and identify potential bugs. But each contribution or security report still needs review—and that work can become the bottleneck. OpenSSL’s growing report volume and a Linux Foundation survey of open-source contributors show both sides of the trade-off: faster development, but more material for maintainers to assess. 1
21
OpenSSL provides software used to secure internet communications, making the quality and security of its code important well beyond the project itself. 1
5
At the project’s annual conference in Prague, executive director Matt Caswell said OpenSSL received an average of 71 security reports and inquiries per month from May through July 2026, compared with nine per month during the same period a year earlier. The total reached 108 inquiries in August. 1
Those figures describe incoming reports and inquiries—not confirmed vulnerabilities. Over the preceding year, OpenSSL received roughly 500 vulnerability reports, but 63 resulted in disclosed vulnerabilities. Many submissions were duplicates, minor defects, or issues that did not warrant a security advisory. Most vulnerabilities found with AI tools were low severity, rather than major security flaws. Even so, submissions take human effort to assess. 1
3
The added review pressure is not unique to OpenSSL. Maintainers from Bouncy Castle and cryptlib also described having more reports to examine at the conference. Bouncy Castle’s Megan Woods warned about the risks of AI-authored cryptographic code, reinforcing the need to treat generated code with care. 2
3
AI tools can help with tasks such as reviewing code, investigating reported vulnerabilities, and writing tests, according to OpenSSL’s chief technology officer. 3 These uses may support maintainers’ work, but they do not make a potential finding a confirmed flaw or remove the need for human assessment.
1
3
That distinction matters because discovery and verification are different jobs. A tool can surface a suspicious code path or produce a plausible report; maintainers still need to determine whether it describes a real, relevant issue and what to do about it. The conference reporting says investigations, patch development, and security-advisory publication can take six to eight weeks. 3
A Red Hat-sponsored Linux Foundation Research survey, presented at All Things Open, found that maintainers estimated 25% of incoming pull requests were low-quality “AI slop.” The share rose to 31% at large projects. The survey covered 234 open-source contributors and maintainers. 20
21
At the same time, 59% of project maintainers reported an increase in contributions. 21 More submissions can bring useful work and new contributors, but the volume also adds review demands—particularly when contributions arrive with problems that maintainers must identify and explain.
The findings are survey estimates, not a count of every pull request across open-source projects. They nevertheless point to a practical challenge: AI can reduce the effort involved in producing a contribution without reducing the effort required to decide whether it is ready to merge. 20
21
Google’s response shows how increased intake can affect security-reporting programs. On October 1, it paused new product-vulnerability submissions to its Open Source Software Vulnerability Reward Program, citing a rise in automated submissions, the vast majority of which it said were invalid. Google said it would provide an update in the first quarter of 2027. The pause applied to product-vulnerability submissions to that program, not every Google vulnerability-reward program. 18
For open-source projects, the evidence points to a balanced approach: make contribution expectations clear, ask for reproducible evidence and tests where relevant, and use automation to help triage—not to bypass human review. Those are practical implications of the reporting, rather than a single prescribed solution. 1
18
21
AI can make it faster to write code and find potential defects. Trustworthy software still depends on maintainers having the time and support to check what arrives.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
AI can speed up coding and surface bugs, but maintainers still have to verify the results.
AI can speed up coding and surface bugs, but maintainers still have to verify the results. A Linux Foundation survey found 25% of incoming pull requests were considered low quality, rising to 31% at large projects.