Skip to main content

Available filters for security overview

Reference for all available filters you can use to narrow security overview data.

Wer kann dieses Feature verwenden?

Zugriff erfordert:

  • Organisationsansichten: Schreibzugriff auf Repositorys in der Organisation
  • Enterprise-Ansichten: Organisationsbesitzerinnen und Sicherheitsmanagerinnen

Organisationen im Besitz eines GitHub Team-Kontos mit GitHub Secret Protection or GitHub Code Security, oder im Besitz eines GitHub Enterprise-Kontos

This article lists all available filters (qualifiers) for security overview. The available filters vary depending on the specific view and whether you are viewing data at the enterprise or organization level.

For information about how to apply filters, see Filtern von Warnungen in der Sicherheitsübersicht.

Hinweis

Die über die Sicherheitsübersicht angezeigten Informationen variieren je nach deinem Zugriff auf Repositorys und Organisationen und je nachdem, ob Advanced Security-Features von diesen Repositorys und Organisationen verwendet werden. Weitere Informationen finden Sie unter Sicherheitsübersicht.

Filter logic for security overview

You can apply filters and use logical operators to display results that meet specific criteria on security overview. By default, if you apply several different filters, you are using AND logic, meaning you will only see results that match every filter you apply. For example, if you add the filter is:public dependabot:enabled, you will only see results from repositories that are public and have Dependabot enabled.

Currently, there are two logical operators that you can apply to your filters on security overview:

  • The - operator applies NOT logic, displaying all results except those that match the specified filter. To use the - operator, add it to the beginning of a filter. For example, filtering for -repo:REPOSITORY-NAME will display data from all repositories except REPOSITORY-NAME.
  • The , operator applies OR logic, displaying results that match any of the specified values for a single filter. To use the , operator, add it between each listed value for a filter. For example, filtering for is:public,private will display data from all repositories that are public or private. Similarly, if you apply the same filter multiple times with different values, you are using OR logic. For example, is:public is:private is equivalent to is:public,private.

Repository name

Available in: All views

  • Free text or keyword search: Display data for all repositories with a name that contains the keyword. For example, search for test to show data for both the "test-repository" and "octocat-testing" repositories.
  • repo qualifier: Display data only for the repository that exactly matches the value of the qualifier. For example, search for repo:octocat-testing to show data for only the "octocat-testing" repository.

Repository visibility and status filters

QualifierDescriptionViews
visibilityDisplay data for all repositories that are public, private, or internal."Overview" and metrics
isDisplay data for all repositories that are public, private, or internal."Risk" and "Coverage"
archivedDisplay only data for archived (true) or active (false) repositories.All except "Alerts" views

Team and topic filters

Available in: All views

QualifierDescription
teamDisplay data for all repositories that the specified team has write access or admin access to. For more information on repository roles, see Repositoryrollen für eine Organisation.
topicDisplay data for all repositories that are classified with a specific topic. For more information on repository topics, see Dein Repository mit Themen klassifizieren.

Custom repository property filters

Available in: Organization-level "Overview" view

Hinweis

Repository properties are in Öffentliche Vorschau and subject to change.

Custom repository properties are metadata that organization owners can add to repositories in an organization, providing a way to group repositories by the information you are interested in. For example, you can add custom repository properties for compliance frameworks or data sensitivity. For more information on adding custom repository properties, see Verwalten von benutzerdefinierten Eigenschaften für Repositorys in Ihrer Organisation.

If you add custom properties to your organization and set values for repositories, you can filter the "Overview" using those custom properties as qualifiers.

QualifierDescription
props.CUSTOM_PROPERTY_NAMEThe qualifier consists of a props. prefix, followed by the name of the custom property. For example, props.data_sensitivity:high displays results for repositories with the data_sensitivity property set to the value high.

Repository owner filters

Available in: Enterprise-level views

QualifierDescription
orgDisplay data for repositories owned by one organization.

Security feature enablement filters

Available in: "Risk" and "Coverage" views

QualifierDescription
code-scanning-alertsDisplay repositories that have configured code scanning.
dependabot-alertsDisplay repositories that have enabled Dependabot alerts.
secret-scanning-alertsDisplay repositories that have enabled Warnungen zur Geheimnisüberprüfung.
any-featureDisplay repositories where at least one security feature is enabled.

Extra filters for the "Coverage" view

QualifierDescription
code-scanning-default-setupDisplay data for repositories where code scanning is enabled or not enabled using CodeQL default setup.
code-scanning-pull-request-alertsDisplay data for repositories where code scanning is enabled or not enabled to run on pull requests.
dependabot-security-updatesDisplay data for repositories where Dependabot security updates is enabled or not enabled.
secret-scanning-push-protectionDisplay data for repositories where push protection for secret scanning is enabled or not enabled.

Alert number filters

Available in: "Risk" view

QualifierDescription
code-scanning-alertsDisplay data for repositories that have exactly (=), more than (>) or fewer than (<) a specific number of code scanning alerts. For example: code-scanning-alerts:>100 for repositories with more than 100 alerts.
dependabot-alertsDisplay data for repositories that have a specific number (=), more than (>) or fewer than (<) a specific number of Dependabot alerts. For example: dependabot-alerts:<=10 for repositories with fewer than or equal to 10 alerts.
secret-scanning-alertsDisplay data for repositories that have a specific number (=), more than (>) or fewer than (<) a specific number of Warnungen zur Geheimnisüberprüfung. For example: secret-scanning-alerts:=10 for repositories with exactly 10 alerts.

Alert type and property filters

Available in: "Overview" view

Alert type filters

QualifierDescription
tool:codeqlShow data only for code scanning alerts generated using CodeQL.
tool:dependabotShow data only for Dependabot alerts.
tool:secret-scanningShow data only for Warnungen zur Geheimnisüberprüfung.
tool:githubShow data for all types of alerts generated by GitHub tools.
tool:third-partyShow data for all types of alerts generated by third-party tools.
tool:TOOL-NAMEShow data for all alerts generated by a third-party tool for code scanning.

Alert property filters

QualifierDescription
codeql.ruleDisplay data only for code scanning identified by a specific rule for CodeQL.
dependabot.ecosystemDisplay data only for Dependabot alerts for a specific ecosystem, for example: npm.
dependabot.packageDisplay data only for Dependabot alerts for a specific package, for example: tensorflow.
dependabot.scopeDisplay data only for Dependabot alerts with a runtime or development scope.
secret-scanning.bypassedDisplay data only for Warnungen zur Geheimnisüberprüfung where push protection was bypassed (true) or not bypassed (false).
secret-scanning.providerDisplay data only for Warnungen zur Geheimnisüberprüfung issued by a specific provider, for example: secret-scanning.provider:adafruit.
secret-scanning.secret-typeDisplay data only for Warnungen zur Geheimnisüberprüfung for a specific type of secret, for example: secret-scanning.secret-type:adafruit_io_key.
secret-scanning.validityDisplay data only for Warnungen zur Geheimnisüberprüfung for a specific validity (active, inactive, or unknown).
severityDisplay data only for alerts of a specific severity (critical, high, medium, or low).
third-party.ruleDisplay data only for code scanning identified by a specific rule for a tool developed by a third party. For example, third-party.rule:CVE-2021-26291-maven-artifact shows only results for the CVE-2021-26291-maven-artifact rule of a third-party code scanning tool.

Production context filters

Available in: Dependabot and code scanning views

Hinweis

Die Integration mit Microsoft Defender for Cloud ist in Öffentliche Vorschau und kann geändert werden.

For more information about production context, see Priorisieren von Dependabot- und Codeüberprüfungswarnungen mithilfe des Produktionskontexts.

QualifierDescription
artifact-registry or artifact-registry-urlDefines the name or location of the artifact registry used by the repository. For example: artifact-registry:jfrog-artifactory or artifact-registry-url:my-registry.example.com.

Uses metadata from the Storage Record API.
has: deploymentLimits alerts to those reported as in deployment.

Uses metadata from the Deployment Record API.
runtime-riskLimits alerts to those reported as presenting a specific type of runtime risk. For example: runtime-risk:internet-exposed

Uses metadata from the Deployment Record API.

Dependabot view filters

Available in:

  • Dependabot view
  • Dependabot malware alerts view
QualifierDescription
assigneeDisplay alerts by assignee username or team, for example: assignee:@octocat, assignee:@copilot, or assignee:@github/security-team.
ecosystemDisplay Dependabot alerts detected in a specified ecosystem, for example: ecosystem:Maven.
epss_percentageDisplay Dependabot alerts whose EPSS score meets the defined criteria, for example: epss_percentage:>=0.01
hasDisplay Dependabot alerts for vulnerabilities where either a secure version is already available (patch) or where at least one call from the repository to a vulnerable function is detected (vulnerable-calls). For more information, see Anzeigen und Aktualisieren von Dependabot-Warnungen.
isDisplay Dependabot alerts that are open (open) or closed (closed).
packageDisplay Dependabot alerts detected in the specified package, for example: package:semver.
propsDisplay Dependabot alerts for repositories with a specific custom property set. For example, props.data_sensitivity:high displays results for repositories with the data_sensitivity property set to the value high.
relationshipDisplay Dependabot alerts detected in direct (relationship:direct) or indirect dependencies (relationship:transitive).
repoDisplay Dependabot alerts detected in a specified repository, for example: repo:octo-repository.
resolutionDisplay Dependabot alerts closed as "auto-dismissed" (auto-dismissed), "a fix has already been started" (fix-started), "fixed" (fixed), "this alert is inaccurate or incorrect" (inaccurate), "no bandwidth to fix this" (no-bandwidth), "vulnerable code is not actually used" (not-used), or "risk is tolerable to this project" (tolerable-risk).
scopeDisplay Dependabot alerts from the development dependency (development) or from the runtime dependency (runtime).
severityDisplay Dependabot alerts of the specified severity, for example: severity:critical.
sortGroups Dependabot alerts by the manifest file path the alerts point to (manifest-path) or by the name of the package where the alert was detected (package-name). Alternatively, displays alerts from most important to least important, as determined by CVSS score, vulnerability impact, relevancy, and actionability (most-important), from newest to oldest (newest), from oldest to newest (oldest), or from most to least severe (severity).
teamDisplay Dependabot alerts owned by members of the specified team, for example: team:octocat-dependabot-team.
topicDisplay Dependabot alerts with the matching repository topic, for example: topic:asdf.

Dependabot dashboard filters

Available in: Dependabot dashboard view

QualifiziererBeschreibung
repoAnzeigen von Dependabot alerts, die in einem angegebenen Repository erkannt wurden, z. B.: repo:octo-repository.
topicZeige Dependabot alerts mit dem entsprechenden Repositorythema an, z. B.: topic:asdf.
teamAnzeigen von Dependabot alerts, die Mitgliedern des angegebenen Teams gehören, z. B.: team:octocat-dependabot-team.
visibilityAnzeigen von Dependabot alerts, die in Repositorys der angegebenen Sichtbarkeit erkannt wurden, z. B.: visibility:private.
archivedAnzeigen von Dependabot alerts, die in komplett archivierten oder komplett nicht archivierten Repositorys erkannt wurden, z. B.: archived:true.
stateAnzeigen von Dependabot alerts des angegebenen Zustands, z. B.: state:unresolved.
severityAnzeigen von Dependabot alerts des angegebenen Schweregrads, z. B.: severity:critical.
scopeZeigen Sie Dependabot alerts aus der Entwicklungsabhängigkeit (development) oder aus der Runtime-Abhängigkeit (runtime) an.
packageZeigen Sie Dependabot alerts an, die im angegebenen Paket erkannt wurden, z. B.: package:lodash.
ecosystemZeigen Sie Dependabot alerts an, die in einem angegebenen Ökosystem erkannt wurden, z. B.: ecosystem:Maven.
relationshipAnzeigen von Dependabot alerts der angegebenen Beziehung, z. B.: relationship:indirect.
epss_percentageAnzeigen von Dependabot alerts, deren EPSS-Score die definierten Kriterien erfüllt, z. B.: epss_percentage:>=0.01
exclude <QUALIFIER>Gilt für alle verfügbaren Qualifizierer.
Anzeigen von Benachrichtigungen, die nicht mit dem ausgewählten Qualifizierer aus der Liste der Dependabot alerts übereinstimmen

Alternatively, you can use complex filters by clicking Filter and build custom filters to suit your needs.

Code scanning view filters

Available in: code scanning view

You can click any result to see full details of the relevant query and the line of code that triggered the alert.

QualifierDescription
isDisplay code scanning alerts that are open (open) or closed (closed).
resolutionDisplay code scanning alerts closed as "false positive" (false-positive), "fixed" (fixed), "used in tests" (used-in-tests), or "won't fix" (wont-fix).
ruleDisplay code scanning alerts identified by the specified rule.
severityDisplay code scanning alerts categorized as critical, high, medium, or low security alerts. Alternatively, displays code scanning alerts categorized as error, warning, note problems.
sortDisplay alerts from newest to oldest (created-desc), oldest to newest (created-asc), most recently updated (updated-desc), or least recently updated (updated-asc).
toolDisplay code scanning alerts detected by the specified tool, for example: tool:CodeQL for alerts created using the CodeQL application in GitHub.

Secret scanning view filters

Available in: secret scanning view

QualifierDescription
bypassedDisplay Warnungen zur Geheimnisüberprüfung where push protection was bypassed (true) or not bypassed (false).
isDisplay Warnungen zur Geheimnisüberprüfung that are open (open), closed (closed), publicly leaked (publicly-leaked), or multi-repository (multi-repository).
propsDisplay alerts for repositories with a specific custom property set. For example, props.data_sensitivity:high displays results for repositories with the data_sensitivity property set to the value high.
providerDisplay alerts for all secrets issued by a specified provider, for example: adafruit.
repoDisplay alerts detected in a specified repository, for example: repo:octo-repository.
resolutionDisplay Warnungen zur Geheimnisüberprüfung closed as "false positive" (false-positive), "hidden by config" (hidden-by-config), "pattern deleted" (pattern-deleted), "pattern edited" (pattern-edited), "revoked" (revoked), "used in tests" (used-in-tests), or "won't fix" (wont-fix).
resultsDisplay default (default) or generic (generic) Warnungen zur Geheimnisüberprüfung.
secret-typeDisplay alerts for the specified secret and provider (provider-pattern) or custom pattern (custom-pattern).
sortDisplay alerts from newest to oldest (created-desc), oldest to newest (created-asc), most recently updated (updated-desc), or least recently updated (updated-asc).
teamDisplay alerts owned by members of the specified team, for example: team:octocat-dependabot-team.
topicDisplay alerts with the matching repository topic, for example: topic:asdf.
validityDisplay alerts for a specific validity (active, inactive, or unknown).