Investigate gaps in a security report

In Reviews → Security report, compare the selected window's findings with its Coverage gaps to find repositories and reviews that lack completed analyzer results.

Read the coverage gaps#

Coverage gaps lists what the counts do not include. Every member sees it, so an exported or shared report never reads as a complete analysis. Each line gives a count:

  • Reviews with no finished analyzer run: reviews in the window that static analysis did not finish or never ran on.
  • A failed or cut-short analysis, such as Secret scan was cut short: its output was too large., with how many runs it affected.
  • Application security findings that cite no CWE: findings the report cannot place in a category or rank.
  • Incomplete assessments, by cause: assessments in the window that ended incomplete, by why they stopped. Each cause the Reviews search supports opens the matching reviews.
  • Repositories with no finished analyzer run in the window, each linked to its repository page.

When static analysis is off for the organization, the report says so above the counts. New reviews then run no analyzers, and their findings cite no CWE. An administrator turns it on with Open code review settings. When the deployment offers no static analysis, the report says it has nothing to count.

Search help

Tab to a result. Enter to open. Escape to close.