The Dashboard is the central screen of any project on Codacy. After Codacy has cloned the project and run the first analysis, data will populate the dashboard and help you answer two main questions on your project:
- what is the current state of the repository's code quality? You can see more on that in our Code Dashboard
- how is it evolving through time?
The History Dashboard provides a fast overview of your project quality status and evolution. You can choose to see how your project has evolved over the past 7 or 31 days and also see a prediction about the evolution of your code quality if you continue the trend of the past days.
At the center you can see 4 tabs, each regarding the evolution of one code quality metric:
Each chart contains a green area (except coverage which contains a red area), where you can see what is defined as acceptable/good on your project quality settings. On the Coverage tab, the red area shows what is defined as under the quality parameters defined in the project quality settings.
On the right side there are 3 tables with more information:
- Issues Breakdown by category. For example, you can see how many security issues you have, as well as it's evolution on the time span you've selected.
- Issues/ Lines of code - shows the evolution of the issues by lines of code ratio.
- Technical debt - the evolution of the estimated technical debt time of your project. This is calculated using the found issues, and the estimated time to fix all of them.
This chart compares your project issues per line of code ratio with the industry standard. If you are interested in better understanding the industry standard read our documentation.
This chart shows the evolution of cyclomatic complexity on your project.
Cyclomatic Complexity is a software metric (measurement), used to indicate the complexity of a program. It is a quantitative measure of the number of linearly independent paths through a program's source code.
The chart shows the percentage of complex files on your project. A complex file is a file with a complexity value bigger than the threshold defined on the project quality settings.
The complexity value of a file is defined by the most complex method in it.
This chart shows the percentage of duplicated files as well as the evolution of duplication on your project. A duplicated file is a file with a number of clones value bigger than the threshold defined on the project quality settings
A clone is a set of code blocks with a very big percentage of similarity.
This chart shows the evolution of code coverage on your project.
Code coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs. While there are several coverage criteria, we focus on Line coverage, i.e. we analyse the percentage of lines covered in tests.
The chart shows coverage values received for your project. As in all the other charts, the threshold can be defined on the project quality settings