Astro’s GitHub issue backlog is heading to zero for the first time in 5 years. Now Cloudflare is open-sourcing the tool that did it.

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Most open source maintainers will know the feeling of opening GitHub to a growing pile of issues that can’t feasibly be maintained by a small team. AI coding tools have made things worse: a low-effort bug report, an unreviewed patch, or a speculative vulnerability write-up can all be generated in seconds now, but working out whether any of it holds up still takes a person just as long as it always did.

However, the team behind one popular open source project has reported that it’s on track to clear its issue backlog entirely, by handing the grunt work to a team of agents.

Astro, the JavaScript framework used to build fast, content-heavy websites, is down to around 20 open GitHub issues at the time of writing, from more than 200 at the start of this year — and the team expects to hit zero within the next month, which would be a first in the project’s five-year history. It’s getting there using a team of AI subagents built by its own team, and Cloudflare, which acquired that team in January, announced on Tuesday that it’s open-sourcing the systems for other maintainers to use.

Astro finds its fix

The tool, called triagebot-action, runs as a GitHub Action. When someone opens an issue, it kicks off a four-stage pipeline: reproduce the bug in a sandbox, diagnose the root cause, verify it’s an actual bug, and attempt a fix. Each stage is handled by a separate AI agent, and the whole process is driven by a state machine encoded in GitHub labels, so anyone can see exactly where a given issue sits and why.

“‘Fix’ is always the hardest because the bar is so high.”

Fred Schott, …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/cloudflare-astro-triage-bot/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.