Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Coding-agent traces in advisory fixes

Written November 10, 2026

A preprint mining GitHub Security Advisories found traces of coding agents in the fixes for hundreds of advisories. It counts traces, not quality — and association is not proof that agents fix bugs better.

The problem

A team deciding whether to let agents touch security fixes has mostly marketing to go on. Vendors say agents fix vulnerabilities; skeptics say agents introduce them. Neither side has had much evidence of what agents actually do in real fixes, in public repositories, where the work can be checked.

What the study found

The paper, Agents on the Patch Path, submitted November 6, looks for observable evidence of coding-agent involvement in commits referenced by reviewed GitHub Security Advisories. The authors built a mining pipeline that flags agent evidence through known agent accounts, explicit commit-message attribution, repository instruction files, and agent configuration artifacts. Linking those findings to advisory-referenced commits gives 469 valid candidate advisories across 189 repositories, including 448 with direct attribution and 21 supported only by repository-level evidence. Claude is the most frequently observed tool family, followed by Copilot and Cursor.

The candidate advisories include high- and critical-severity vulnerabilities, so this is not a corner of trivial fixes. The authors also compared review timing: against advisories published in the same months, candidate advisories show a modestly longer mean review lag, mostly from timing within the same disclosure routes rather than from a different mix of routes. Against a historical baseline, they show substantially shorter mean review lags, with both route mix and within-route timing contributing.

What it does not show

What a team can take from it

The useful finding is a modest one: coding-agent involvement in security remediation is already observable across hundreds of advisories and repositories, including severe ones. That means agent-written code in security fixes is no longer a hypothetical to plan for — it is already in the patch history of real projects. The questions the study leaves open are the ones a team still has to answer for itself: who reviews agent-written security patches, how thoroughly, and what happens when the agent's fix is wrong.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Secret scanning now catches Actions log leaks · Apiiro: 1,122 Claude settings files leak secrets