Skip to main content

Filtering alerts in the security overview

Use filters to view specific categories of alerts

Who can use this feature

Organization owners and security managers can access the organization-level security overview and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager. Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.

All organizations and enterprises have a security overview. If you use GitHub Advanced Security you will see additional information. For more information, see "About GitHub Advanced Security."

About filtering the security overview

You can use filters in a security overview to narrow your focus based on a range of factors, like alert risk level, alert type, and feature enablement. Different filters are available depending on the specific view and whether you are viewing data at the enterpise or organization level.

The information shown in the security overview will vary according to your access to repositories, and on whether GitHub Advanced Security is used by those repositories.

Filter by repository

QualifierDescription
repo:REPOSITORY-NAMEDisplays data for the specified repository.

Filter by whether security features are enabled

In the examples below, replace :enabled with :not-enabled to see repositories where security features are not enabled. These qualifiers are available in the main summary views.

QualifierDescription
code-scanning:enabledDisplay repositories that have set up code scanning.
dependabot:enabledDisplay repositories that have enabled Dependabot alerts.
secret-scanning:enabledDisplay repositories that have enabled secret scanning alerts.
any-feature:enabledDisplay repositories where at least one security feature is enabled.

The organization-level Security Coverage view includes extra filters.

Note: The "Security Risk" and "Security Coverage" views are currently in beta and subject to change.

QualifierDescription
code-scanning-pull-request-alerts:enabledDisplay repositories that have configured code scanning to run on pull requests.
dependabot-security-updates:enabledDisplay repositories that have enabled Dependabot security updates.
secret-scanning-push-protection:enabledDisplay repositories that have set up push protection for secret scanning.

Filter by repository type

These qualifiers are available in the main summary views.

QualifierDescription
is:publicDisplay public repositories.
is:internalDisplay internal repositories.
is:privateDisplay private repositories.
archived:trueDisplay archived repositories.
archived:falseOmit archived repositories.

Filter by level of risk for repositories

The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk.

These qualifiers are available in the enterprise-level view.

QualifierDescription
risk:highDisplay repositories that are at high risk.
risk:mediumDisplay repositories that are at medium risk.
risk:lowDisplay repositories that are at low risk.
risk:unknownDisplay repositories that are at an unknown level of risk.
risk:clearDisplay repositories that have no detected level of risk.

Filter by number of alerts

These qualifiers are available in the enterprise-level Overview and in the organization-level Security Risk view.

QualifierDescription
code-scanning:nDisplay repositories that have n code scanning alerts. This qualifier can use =, > and < comparison operators.
secret-scanning:nDisplay repositories that have n secret scanning alerts. This qualifier can use =, > and < comparison operators.
dependabot:nDisplay repositories that have n Dependabot alerts. This qualifier can use =, > and < comparison operators.

Filter by team

These qualifiers are available in the main summary views.

QualifierDescription
team:TEAM-NAMEDisplays repositories that TEAM-NAME has admin privileges for.

Filter by topic

These qualifiers are available in the main summary views.

QualifierDescription
topic:TOPIC-NAMEDisplays repositories that are classified with TOPIC-NAME.

Additional filters for code scanning alert views

All code scanning alerts have one of the categories shown below. You can click any result to see full details of the relevant query and the line of code that triggered the alert.

QualifierDescription
severity:criticalDisplays code scanning alerts categorized as critical.
severity:highDisplays code scanning alerts categorized as high.
severity:mediumDisplays code scanning alerts categorized as medium.
severity:lowDisplays code scanning alerts categorized as low.
severity:errorDisplays code scanning alerts categorized as errors.
severity:warningDisplays code scanning alerts categorized as warnings.
severity:noteDisplays code scanning alerts categorized as notes.

Additional filters for Dependabot alert views

You can filter the view to show Dependabot alerts that are ready to fix or where additional information about exposure is available. You can click any result to see full details of the alert.

QualifierDescription
has:patchDisplays Dependabot alerts for vulnerabilities where a secure version is already available.
has:vulnerable-callsDisplays Dependabot alerts where at least one call from the repository to a vulnerable function is detected. For more information, see "Viewing and updating Dependabot alerts."

Additional filters for secret scanning alert views

QualifierDescription
provider:PROVIDER_NAMEDisplays alerts for all secrets issues by the specified provider.
secret-type:SERVICE_PROVIDERDisplays alerts for the specified secret and provider.
secret-type:CUSTOM-PATTERNDisplays alerts for secrets matching the specified custom pattern.

For more information, see "Secret scanning patterns."