Claude Code has about 15,000 open issues - of which ~2/3rds are labeled as bugs - in a code base that was around 500 KLOC when the source leaked.
But sure, tell us again about your amazing code review tool.
To put it into perspective, the JUnit 5 framework has about 100 KLOC and one open bug.
@jasongorman this
Oct 18, 2026, 3:25 AM@jasongorman If you have to worry about whether the current thing is in cents or dollars, then perhaps the real problem you have is Primitive Obsession.
Claude would never call *that* problem out, of course.
@philip Primitive Obsession is the LLM's go-to design style
Yes. And that's a pretty good data point for Test-Driven Development (TDD).
@JeffGrigg One of the AI stans on LinkedIn read my post and immediately asked Claude to find bugs in the JUnit framework. It found a handful. And I couldn't reproduce the two I picked randomly.
Other folks say "This is just evidence that Claude Code is very popular". Yes, that would explain why it has 2000x the reported defect density of a unit testing framework used in millions of code bases for over a decade.
@jasongorman 15,000 open issues doesn’t count the issues closed automatically because nobody fixed them in time.
@natpryce Yup. I can't find it now, but some published a whole bunch of analysis on their issues database. Fix times are getting longer and longer, and most issues are closed without being resolved.
And the # of bugs reported per day is expanding, of course.
I recognise the product trajectory, but I've never seen it happen this fast before.
@jasongorman @natpryce this one? Resolution times per month, week-sized blocks. Blue open, green within 4 weeks, yellow within a quarter, orange within a year
@jasongorman @StOnSoftware David Denton also published some articles on LinkedIn of his analysis of the issue tracker data
@StOnSoftware @natpryce Certainly looks similar
That's about one known bug every 33 lines!
... which is, unfortunately, believable.
😮💨 💢