{"meta":{"title":"Interpreting the code quality results for your repository","intro":"View GitHub Code Quality findings for your default branch.","product":"Security and code quality","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/code-security","title":"Security and code quality"},{"href":"/en/enterprise-cloud@latest/code-security/how-tos","title":"How-tos"},{"href":"/en/enterprise-cloud@latest/code-security/how-tos/maintain-quality-code","title":"Maintain quality code"},{"href":"/en/enterprise-cloud@latest/code-security/how-tos/maintain-quality-code/interpret-results","title":"Interpret results"}],"documentType":"article"},"body":"# Interpreting the code quality results for your repository\n\nView GitHub Code Quality findings for your default branch.\n\n> \\[!NOTE]\n> GitHub Code Quality is currently in public preview and subject to change.\n> During public preview, Code Quality will not be billed, although Code Quality scans will consume GitHub Actions minutes.\n\n## Prerequisites\n\n* Code Quality is enabled, see [Enabling GitHub Code Quality](/en/enterprise-cloud@latest/code-security/code-quality/how-tos/enable-code-quality).\n\n## Viewing the full backlog of code quality results\n\n1. Navigate to the ** Security and quality** tab of your repository.\n2. Click to expand ** Code quality**, then click **Standard findings**.\n\nAlternatively, if you want to view AI-powered findings for the most recently changed files, see [Improving the quality of recently merged code with AI](/en/enterprise-cloud@latest/code-security/code-quality/tutorials/improve-recent-merges).\n\n## Exploring the backlog for your repository\n\nThe \"Standard findings\" dashboard shows all the results found by CodeQL analysis on the default branch of your repository. This view helps you visualize the full backlog of quality results and prioritize work to fix specific types of problems.\n\nThe overview, at the top of the page, summarizes the maintainability and reliability of the codebase.\n\n\n\nUnderneath the overview, the full list of results is shown with a header with filters that you can use to focus on a specific set of findings. The results are:\n\n* Grouped by the rule that detected each finding\n* Within each rule, ordered by file path alphabetically\n\nExplore the results by expanding a rule to list the affected files and clicking on the name of a rule to see full details of the findings.\n\n\n\n## Interpreting ratings and metrics\n\nCode quality results should always be interpreted in the context of your repository. For example:\n\n* Small repositories, or repositories with only a small amount of code written in supported languages, tend to have few results and good ratings.\n* Repositories with a lot of generated code may have many maintenance results, lowering the rating for maintainability. This is not a problem if the source code itself is maintainable.\n* Large repositories with a lot of code in a fully supported language often have many results even if the majority of the code has good maintainability and reliability standards.\n\nTo learn more about the metrics and how the ratings are calculated, see [Metrics and ratings reference](/en/enterprise-cloud@latest/code-security/code-quality/reference/metrics-and-ratings).\n\n## Next steps\n\n* Remediate quality findings in your default branch and improve the maintainability and reliability rating for your repository. See [Improving the quality of your repository's code](/en/enterprise-cloud@latest/code-security/code-quality/tutorials/improve-your-codebase).\n* Stop your repository from accumulating more code quality problems by setting a quality threshold for pull requests using rulesets. See [Setting code quality thresholds for pull requests](/en/enterprise-cloud@latest/code-security/code-quality/how-tos/set-pr-thresholds)."}