A data-driven analysis examining whether Claude-assisted commits introduced more bugs into rsync releases. Using severity-weighted bugs per 10 commits as the primary metric, the analysis applies permutation tests and Fisher's exact test across all rsync releases. The two Claude-exposed releases (v3.4.2 and v3.4.3) fall within the historical interquartile range — one below, one above — with no statistically significant difference from non-Claude releases. The worst release in rsync history predates Claude entirely. The analysis also addresses a key confounder: a flood of AI-generated CVE reports forced rapid security changes, which caused regressions unrelated to Claude's code quality. The broader context is an online outrage cycle that escalated from a Mastodon post to a GitHub issue with 350+ comments and harassment, driven by pre-existing anti-AI sentiment rather than empirical evidence.

19m read timeFrom alexispurslane.github.io
Post cover image
Table of contents
0 · Disclaimer: How AI Assistance Was Used1 · Background: The rsync Outrage2 · Executive Summary3 · The Metric4 · Results5 · What the Data Is Consistent And Inconsistent WithDiscussion, and Tridge's Response
3.9K Impressions2 Comments