Skip to content
This documentation is a preview of the pull request #2614

For the latest updates and improvements in production, open docs.codacy.com instead.

Organization overview#

Codacy provides high-level visibility into your organization's code quality, security posture, AI risk, usage, and configuration metrics. The Organization overview consolidates these signals in a single view.

The Organization overview summarizes repositories in your Git provider organization that you follow on Codacy. Use it to compare repository status and identify areas that require action.

To open the Organization overview, select an organization in the top navigation bar, then select Overview in the left sidebar.

Image of the Organization Overview on the Overview tab

The Organization overview includes the following tabs:

Use the filters at the top of the page to scope all dashboard data by repositories or segments. For example, filter by repositories owned by specific teams, repositories using specific languages, or exclude legacy repositories that are no longer maintained. Filter selections are stored in your browser and persist across visits.

This page documents the Overview, Grade, Complexity, Duplication, and Coverage sections.

Note

You can use the Codacy API to generate reports or obtain information about the code quality of your repositories in a more flexible way.

For more information see the list of available API endpoints and the following examples:

Overview#

The Organization overview page includes the following areas to help you monitor repository health:

This page also includes the Organization setup area, which provides a checklist of recommended actions to ensure your organization is configured correctly and fully using Codacy capabilities.

Code health and security#

Image of Code health and security section

The Code health and security area provides an organizational snapshot and highlights key hotspots. It shows open issues, new vs. fixed issues, prevented issues, and complexity, duplication, coverage, and security metrics. Select any metric to open detailed results.

Some metrics depend on your billing plan and use plan-specific calculations. For details, see the following table:

Metric Availability How it is calculated
Open issues, New and Fixed issues, and Prevented issues Paid plans More details
Grade Open source and trial plans More details
Complexity All plans More details
Duplication All plans More details
Coverage All plans 1 More details
Security All plans More details

Important

  • The Code health and security area calculates and displays metrics only for repositories you follow on Codacy. As a result, users with different followed repositories can see different values.

  • Some organization-level metrics are limited to the 100 most recently updated repositories, depending on the metric and plan.

1: Coverage metrics are calculated differently for paid plans versus open source and trial plans. Learn more.

Last updated repositories#

The Last updated repositories list shows repositories sorted by most recent update first.

Last updated repositories

Note

The source of the "last updated" value depends on your Git provider:

Grade#

Image of the Grade tab

The Grade tab shows grade distribution across repositories. Use this view to identify higher-risk repositories by selecting a grade in the distribution chart.

At organization level, Grade is the average grade across the 100 most recently updated repositories.

For calculation details, see how metrics are calculated.

Complexity#

Image of the Complexity tab

The Complexity tab helps identify repositories where code may be harder to test and more defect-prone.

At organization level, Complexity is the percentage of complex files across the 100 most recently updated repositories.

This tab shows your organization's complexity status (based on complex file counts) and how repositories compare against configured goals. A file is considered complex when its cyclomatic complexity exceeds the repository-level goal. For details, see how metrics are calculated.

The panel classifies the top 100 most recently updated repositories as above goal, below goal, or without a goal. Because lower complexity is better, repositories above goal are highlighted for review.

At the bottom of the tab, complex-file distribution shows whether files above goal, below goal, or without goals are driving complexity. Repository goal distributions are filterable; file-level data is not.

Duplication#

Image of the Duplication tab

The Duplication tab identifies repeated code sequences that appear in at least two locations in a repository.

At organization level, Duplication is the average duplication across the 100 most recently updated repositories.

This tab shows average duplication and indicates which repositories are above goal, below goal, or without configured goals.

For metric details, see how duplication is calculated.

Coverage#

The Coverage tab provides organization-level visibility into coverage status. Higher coverage helps reduce regression risk when code changes.

At organization level, Coverage depends on your plan:

  • On trial and open source plans, it is the average coverage across the 100 most recently updated repositories.
  • On paid plans, it is a line-based percentage calculated as coveredLines / coverableLines across repositories that report coverage.

For calculation details, see how code coverage is calculated.

Coverage dashboard on Paid plans#

Image of the Coverage tab

The Coverage tab on paid plans uses two key metrics:

  • Covered lines: Number of covered lines reported to Codacy.
  • Coverable lines: Number of lines that can be covered, based on coverage reports.

These metrics drive all dashboard components:

Metric Description
Coverage coveredLines / coverableLines
Aggregation of all covered lines divided by all coverable lines across all repositories (or the current filter selection, see filters). Includes only repositories reporting coverage.
Repositories reporting coverage Repositories with coverage data from the latest merged pull request. For example, if the latest merged pull request reported coverage metrics to Codacy, that repository is counted as reporting coverage.
Coverage trend Time-based trend for covered lines, uncovered lines, and organization coverage (or the current filter selection, see filters). You can choose time ranges and granularities, and select a date to see which repositories changed the most during that period.

You can export data from each chart using the ellipsis icon in the top-right corner in JSON or CSV format.

See also#

Share your feedback 📢

Did this page help you?

Thanks for the feedback! Is there anything else you'd like to tell us about this page?

We're sorry to hear that. Please let us know what we can improve:

Alternatively, you can create a more detailed issue on our GitHub repository.

Thanks for helping improve the Codacy documentation.

Edit this page on GitHub if you notice something wrong or missing.

If you have a question or need help please contact support@codacy.com.

Last modified February 24, 2026