SonarQube

Hmm

... you know, and, and use tools, you know, like, like SonarQube's, uh, clean as you code is, I think a, a great idea.

It just looks at the stuff you've been doing.

Hmm.

And the review takes less time than writing the fix from scratch.

The SonarQube model, generate the fix, verify against the analysis engine, post to the PR, the developer reviews, and clicks one button.

That's maybe 2 minutes versus 30.

The ratio works.

Java benchmark: four thousand four hundred forty-one tasks, one hundred fifty-eight HumanEval, three hundred eighty-six MBPP, and three thousand eight hundred ninety-seven complex code eval tasks.

Analyzer: SonarQube systematic code analysis.

Density metrics are per one thousand lines of code clock.

Category breakdowns are per million lines MLOC.

Two terms worth defining first: cyclomatic complexity counts independent paths through a function.

Cognitive complexity, a SonarQube metric that weights nested and deeply branched logic more heavily, reflecting how hard the code is for a human to read.

Neither one tells you whether the code works.

Both help indicate how much logic reviewers and testers will need to reason through.