Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This plugin is deprecated because it is not compatible with SonarQube 4.2+.



Wiki Markup
{iframe:src=|width=700|height=250|frameborder=0} Your browser does not support iframes. {iframe}

since SonarQube 3.7. Please move to the concept of Technical Debt introduced in SonarQube 4.0.

Description / Features

This plugin is an implementation of the Toxicity Chart visualization technique presented by Erik Dörnenburg on his blog. This technique is useful to quickly get an idea of the general quality of a large existing code base. Toxicity Charts stack multiple static analysis metrics for classes, methods, or components within an application, providing a combined "toxicity" score for each area of the code base. This can be extremely useful in helping managers and non-developers understand the internal quality of the code

Image RemovedImage Added


In a Toxicity Chart each bar represents a class and the height of the bar shows the toxicity score for that class.  The score is based on 11 rules (see Usage & Installation section) and different colours are used to represent each one. This makes it possible to easily spot not only how toxic a code base is, but also how the problems are distributed and what the preponderant "code smell" is. The classes that score zero points are left off the chart. The metrics are computed using the threshold value set for corresponding Checkstyle rule.

Image RemovedImage Added

For example if the Method Length metric has a threshold of 30 and a class comprises three methods, one that is 25 lines, one that is 45 lines and another that is 60 lines long, then the score is calculated to be proportional to the length of the method in relation to the threshold and for the given scenario the class gets 1.5 + 2 = 3.5 points.