{"meta":{"title":"About the tool status page","intro":"The tool status page provides visibility into the health and performance of code scanning tools in your repository.","product":"Security and code quality","breadcrumbs":[{"href":"/en/enterprise-server@3.22/code-security","title":"Security and code quality"},{"href":"/en/enterprise-server@3.22/code-security/concepts","title":"Concepts"},{"href":"/en/enterprise-server@3.22/code-security/concepts/code-scanning","title":"Code scanning"},{"href":"/en/enterprise-server@3.22/code-security/concepts/code-scanning/tool-status-page","title":"Tool status page"}],"documentType":"article"},"body":"# About the tool status page\n\nThe tool status page provides visibility into the health and performance of code scanning tools in your repository.\n\n> \\[!NOTE]\n> Your site administrator must enable code scanning before you can use this feature. For more information, see [Configuring code scanning for your appliance](/en/enterprise-server@3.22/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configuring-code-scanning-for-your-appliance).\n>\n> You may not be able to enable or disable code scanning if an enterprise owner has set a GitHub Code Security policy at the enterprise level. For more information, see [Enforcing policies for code security and analysis for your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).\n\n## What is the tool status page?\n\nThe tool status page shows information about all of your code scanning tools and is a good starting point for debugging problems when code scanning isn't working as expected.\n\n> \\[!NOTE]\n> The tool status page shows tool status at the repository level for the default branch only, not at the organization level.\n\n## Tool status indicators\n\nThe tool status page displays one of three statuses:\n\n* **All configurations are working**: All tools are operating as expected\n* **Some configurations need attention**: Some tools have warnings or non-critical issues\n* **Some configurations are not working**: One or more tools have critical errors\n\n## What information is available\n\n### For all code scanning tools\n\n* Configuration status and health\n* Scan scheduling\n* First and most recent scan times\n* Rules used in scans\n\n### For integrated tools like CodeQL\n\nIn addition to the information listed above, the tool status page for integrated tools provides the following details:\n\n* File coverage percentages by programming language\n* Configuration details for each setup type\n* Specific error messages\n* Downloadable CSV reports of analyzed files\n* Downloadable lists of rules used and alert counts\n\n## How CodeQL defines scanned files\n\nCodeQL reports a file as scanned if some lines of code in that file were processed.\n\n### Interpreted languages\n\n* **Default setup**: Scanned files include all source code files for languages CodeQL can analyze\n* **Advanced setup**: You can use `paths` and `paths-ignore` to define which files to scan. See [Code scanning with CodeQL](/en/enterprise-server@3.22/code-security/concepts/code-scanning/codeql/codeql-code-scanning).\n\n### Compiled languages\n\nThe tool status page reports files present before running autobuild or manual build steps. Files generated during the build process are not shown. See [CodeQL code scanning for compiled languages](/en/enterprise-server@3.22/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages#use-autobuild-for-codeql).\n\n### Coverage calculation\n\nFile coverage percentages respect any files excluded by `paths` and `paths-ignore` configuration properties.\n\n## Understanding file coverage percentages\n\nUse file coverage percentages to debug and improve your analysis:\n\n* **High percentage**: Code scanning is working as expected for that language\n* **Low percentage**: Investigate diagnostic output. See [CodeQL scanned fewer lines than expected](/en/enterprise-server@3.22/code-security/reference/code-scanning/troubleshoot-analysis-errors/fewer-lines-scanned-than-expected)\n* **Zero percentage**: You may have code in languages not currently being analyzed. Update your setup to include these languages. See [Workflow configuration options for code scanning](/en/enterprise-server@3.22/code-security/reference/code-scanning/workflow-configuration-options)\n\n> \\[!NOTE]\n> If you set up both advanced setup and default setup, the tool status page only shows default setup.\n\n## Troubleshooting features\n\nThe tool status page helps you troubleshoot issues through:\n\n* **Error messages**: Explains why tools aren't performing as expected with suggested actions\n* **File coverage data**: Shows which files and languages are being analyzed\n* **Configuration details**: Displays information about each analysis run\n* **Downloadable reports**: Provides CSV reports with detailed file and rule information\n\n## Further reading\n\n* [Use the tool status page for code scanning](/en/enterprise-server@3.22/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning)"}