Skip to main content

About the tool status page

The Seite mit dem Toolstatus provides visibility into the health and performance of code scanning tools in your repository.

Wer kann dieses Feature verwenden?

Benutzer*innen mit Schreibzugriff

Code scanning ist für die folgenden Repositorytypen verfügbar:

  • Öffentliche Repositorys auf GitHub.com
  • Organisationseigene Repositorys für GitHub Team, GitHub Enterprise Cloud oder GitHub Enterprise Server, wobei GitHub Code Security aktiviert sind.

What is the Seite mit dem Toolstatus?

The Seite mit dem Toolstatus 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.

Hinweis

The Seite mit dem Toolstatus shows tool status at the repository level for the default branch only, not at the organization level.

Tool status indicators

The Seite mit dem Toolstatus displays one of three statuses:

  • All configurations are working: All tools are operating as expected
  • Some configurations need attention: Some tools have warnings or non-critical issues
  • Some configurations are not working: One or more tools have critical errors

What information is available

For all code scanning tools

  • Configuration status and health
  • Scan scheduling
  • First and most recent scan times
  • Rules used in scans

For integrated tools like CodeQL

In addition to the information listed above, the Seite mit dem Toolstatus for integrated tools provides the following details:

  • File coverage percentages by programming language
  • Configuration details for each setup type
  • Specific error messages
  • Downloadable CSV reports of analyzed files
  • Downloadable lists of rules used and alert counts

How CodeQL defines scanned files

CodeQL reports a file as scanned if some lines of code in that file were processed.

Interpreted languages

  • Default setup: Scanned files include all source code files for languages CodeQL can analyze
  • Advanced setup: You can use paths and paths-ignore to define which files to scan. See Informationen zu Codescans mit CodeQL.

Compiled languages

The Seite mit dem Toolstatus reports files present before running autobuild or manual build steps. Files generated during the build process are not shown. See CodeQL-Codeüberprüfung für kompilierte Sprachen.

Coverage calculation

File coverage percentages respect any files excluded by paths and paths-ignore configuration properties.

Understanding file coverage percentages

Use file coverage percentages to debug and improve your analysis:

Hinweis

If you set up both advanced setup and default setup, the Seite mit dem Toolstatus only shows default setup.

Troubleshooting features

The Seite mit dem Toolstatus helps you troubleshoot issues through:

  • Error messages: Explains why tools aren't performing as expected with suggested actions
  • File coverage data: Shows which files and languages are being analyzed
  • Configuration details: Displays information about each analysis run
  • Downloadable reports: Provides CSV reports with detailed file and rule information

Further reading