{"slug": "maintainers-dont-need-more-ai-bug-reports-they-need-fixes", "title": "Maintainers don’t need more AI bug reports. They need fixes.", "summary": "A GitHub and Microsoft pilot using Microsoft's Codename MDASH agentic scanning harness and MAI Cyber model produced 99 checked, private vulnerability reports with suggested fixes for six widely used open source projects, and maintainers had fixed 55 of them as of November 15, with 14 fixes already in a release. The harness scanned each project, a GitHub Security Lab AI triage agent built on tailored Copilot skills removed duplicates and verified findings, and seven Microsoft FORGE Lab researchers hand-reviewed results before reports went to maintainers via GitHub private vulnerability reporting. Caddy maintainers fixed all 22 reports they received in a week or less, and one Netty maintainer said finding vulnerabilities is no longer the bottleneck: \"Fixing them is the hard part, and that depends on maintainers.", "body_md": "Maintainers don’t need more AI bug reports. They need fixes.\n\nIn the Codename MDASH pilot, GitHub and Microsoft turned thousands of raw AI findings into 99 checked, private reports with suggested fixes for six widely used open source projects. Maintainers have already fixed more than half.\n\nAI has made finding potential vulnerabilities fast and cheap. Fixing them still takes human judgment, and in open source, that work falls to maintainers. Many are already flooded with AI-generated security findings, including duplicates and reports that aren’t vulnerabilities at all. Another raw scan doesn’t help them. Anyone pointing a new model at a project should ask its maintainers first and come with fixes, not just findings.\n\nAI shouldn’t add to maintainers’ workload. So, with maintainers, GitHub and Microsoft ran a pilot together: could AI help maintainers ship fixes instead of handing them more findings?\n\nGitHub and Microsoft are using Codename MDASH, Microsoft’s multi-model agentic scanning harness, to find and fix security vulnerabilities in widely used open source software, strengthening the foundation that much of the world’s code is built on.\n\nThe process\n\nOur pilot had two goals: send only findings that matter, and never send a maintainer an unverified finding. Here’s how it worked:\n\nFind.Codename MDASH, an AI system from Microsoft Security, scanned each project using Microsoft’s MAI Cyber model and suggested fixes for what it found.\n\nFilter. An AI triage agent from the GitHub Security Lab, built on tailored Copilot skills, removed duplicates, checked validity, and focused on high-impact bugs, so maintainers never had to review raw scan results.\n\nReport privately. Reports reached maintainers through GitHub private vulnerability reporting, with a proof of concept and a suggested fix.\n\nFix. Maintainers decided what to fix, how to fix it, and when.\n\nReports and fixes stayed on GitHub, where maintainers already work.\n\nThe result: Codename MDASH, using Microsoft’s MAI Cyber model, flagged thousands of possible issues across the six projects. After AI triage and hand review by seven Microsoft FORGE Lab researchers, maintainers received 99 private reports. As of November 15, they had fixed 55, and 14 of those fixes were already in a release.\n\nWhat we learned\n\nThese lessons come from what the six projects fixed and what their maintainers chose to share. Six projects is a small sample, so read them as early lessons.\n\n1. Fixes matter more than findings\n\nFixing is where maintainers spend their time. So every report arrived already checked, with a suggested fix to review, adapt, and merge. Maintainers started from a well-scoped patch, not a raw finding.\n\nThe first fixes shipped about a week after the initial scan. Caddy’s maintainers fixed all 22 of the reports they received in a week or less. Maintainers used the suggested fixes, some as written and some with changes.\n\nAutoGPT’s maintainers had recently shipped a new check, and it was broken. The report landed three days later and pointed at the right line. They took the fix further than the suggested patch, wrote it within a day, and had it in production less than a week later.\n\nFinding vulnerabilities is no longer our bottleneck. Fixing them is the hard part, and that depends on maintainers.\n\nNetty maintainer\n\n2. Codename MDASH, with researcher review, gave maintainers high-quality findings with fixes\n\nMaintainers got a short list, not a flood. Express maintainers said the reports cut through the noise. Caddy maintainers said they surfaced obscure bugs and filled gaps that earlier reports had missed. For FastMCP, the scan went beyond what AI scanners had given them before. ImageMagick, maintained by a two-person team, received 22 reports.\n\nAI did the finding, researchers did the checking, and maintainers stayed in charge.\n\nOne ImageMagick report looked like a kind of issue the maintainers had seen before. Its summary showed it wasn’t and pointed to the exact lines of code. They were able to push a fix in 15 minutes.\n\nNormally, a security advisory would take us around 30 minutes to 1 hour on average to read, understand, and make a fix. It is a huge difference.\n\nImageMagick maintainer\n\nCodename MDASH was able to find unknown, obscure security bugs in our project with succinct reports, and it filled in gaps from some prior reports that hadn’t been noticed.\n\nCaddy maintainer\n\n3. Open source still has gaps to close\n\nThe pilot worked because people did careful work at every step, and that work doesn’t scale yet. Seven researchers spent about two days per project checking findings by hand. Meanwhile, low-quality reports still reach maintainers every day.\n\nFor open source, fixes need to be delivered via private vulnerability reporting (PVR). Maintainers need to run CI/CD tests on private forks to verify those fixes. And to close the gap between defenders and attackers, maintainers need access to cyber-capable models to verify a proof of concept, before and after the fix.\n\nThe Codename MDASH scan provided unique insights into the security of our project above and beyond what AI scanners have provided us in the past\n\nFastMCP maintainer\n\nWhy it matters\n\nIf you’re a maintainer, this approach changes what a security report costs you. A checked, private report that comes with a suggested fix takes less of your time. You shouldn’t have to triage a scanner’s output. That’s the sender’s job.\n\nIf you use AI to find vulnerabilities in open source, maintainers’ feedback points to this standard:\n\nCheck every finding before you send it, against what the project already knows and against its threat model and security policy.\n\nReport it privately.\n\nInclude a suggested fix. Let maintainers set the pace.\n\nFeatures are easier and easier to ship, but in the future maintaining software will probably come down to who cares enough to manage the security.\n\nAutoGPT maintainer\n\nCodename MDASH is very useful for cutting through the noise of vulnerability reports.\n\nExpress maintainer\n\nWhat you can do today\n\nIf you maintain any open source project, turn on private vulnerability reporting so researchers can report security issues to you without making them public. If your project is on GitHub, turn on core security features in about two minutes with gh-secure.\n\nIf you build on open source, turn on Dependabot alerts so you know when a dependency you use needs a security update.\n\nIf you send AI-generated vulnerability reports to open source projects, hold them to the standard above before you send them.\n\nRepositories using GitHub code security can use agentic autofix to help automatically remediate their alerts with Copilot\n\nWhat happens next\n\nFixes, where maintainers already work. GitHub is bringing these lessons into private vulnerability reporting and security advisories, where GitHub Security Lab is already investing to reduce the burden of low-quality reports on maintainers.\n\nMAI Cyber 2. Today Microsoft announced MAI Cyber 2. The Codename MDASH pilot ran on the earlier MAI Cyber model. GitHub and Microsoft will keep working together to help secure open source.\n\nClosing the gaps, starting with the GitHub Secure Open Source Fund. We’re working with Microsoft to scale researcher review without cutting corners. GitHub will offer every alumni project AI security scans, with findings checked before they’re reported privately. Alumni also get GitHub Copilot Max. We’ll bring this support to future sessions of the Fund.\n\nEveryone downstream benefits from this system. When a maintainer publishes a security advisory on GitHub and it’s reviewed for the GitHub Advisory Database, Dependabot can alert the repositories that depend on that package. That’s the idea behind the GitHub Secure Open Source Fund: 216 projects so far, with more than 300 maintainers fixing more than 4,000 vulnerabilities in software downloaded more than 20 billion times a month.\n\nThank you\n\nTo the maintainers of AutoGPT, Caddy, Express, FastMCP, ImageMagick, and Netty: thank you for your time, your trust, and your feedback. Thank you also to the Codename MDASH team at Microsoft Security, the MAI Cyber team, the researchers of Microsoft FORGE Lab, and GitHub Security Lab.\n\nMaintainers do the fixing. Our job is to make sure they never do it alone.\n\nHear from maintainers about their experience with Codename MDASH. 👇\n\nAbout the GitHub Secure Open Source Fund\n\nAll six projects in this pilot are alumni of the GitHub Secure Open Source Fund, which gives each project $10,000 through GitHub Sponsors, plus security training and a supportive alumni community.\n\nThe GitHub Secure Open Source Fund, powered by GitHub Sponsors, funds open source projects that underpin the digital supply chain, catalyze innovation, and are critical to the AI stack. Want your company to help secure the open source it depends on? Become a funding partner through the Fund page. Learn more about the Fund or apply.\n\nThrough the Fund, maintainers receive security training and Azure credits from Microsoft for Startups. That support sits alongside Microsoft’s European Security Program and its Secure Future Initiative, whose principle is security above all else. Most organizations are downstream in the same way. If your software depends on open source, do the same: back the maintainers you rely on.\n\nI work on open source strategy and programs that support maintainers inside GitHub and across the ecosystem. I also serve on the Steering Committee for the TODO Group, where we help organizations use and sustain open source responsibly.\n\nGit is releasing updates addressing six security vulnerabilities affecting recursive clones, reference handling, merges, binary patches, and imports. Here is what users need to know.\n\nGitHub now highlights ACCESSIBILITY.md files and helps maintainers document accessibility goals, known barriers, supported environments, contributor expectations, and reporting processes.", "url": "https://wpnews.pro/news/maintainers-dont-need-more-ai-bug-reports-they-need-fixes", "canonical_source": "https://github.blog/open-source/maintainers/maintainers-dont-need-more-ai-bug-reports-they-need-fixes/", "published_at": "2026-11-17 18:29:29+00:00", "updated_at": "2026-11-17 19:44:36.628448+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "artificial-intelligence", "ai-tools"], "entities": ["GitHub", "Microsoft", "Codename MDASH", "MAI Cyber", "GitHub Security Lab", "Microsoft FORGE Lab", "Caddy", "Netty"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/maintainers-dont-need-more-ai-bug-reports-they-need-fixes", "markdown": "https://wpnews.pro/news/maintainers-dont-need-more-ai-bug-reports-they-need-fixes.md", "text": "https://wpnews.pro/news/maintainers-dont-need-more-ai-bug-reports-they-need-fixes.txt", "jsonld": "https://wpnews.pro/news/maintainers-dont-need-more-ai-bug-reports-they-need-fixes.jsonld"}}