Skip to main content

Dependabot auto-triage rules

Control how Dependabot handles security alerts, including filtering, ignoring, snoozing, or triggering security updates.

Qui peut utiliser cette fonctionnalité ?

Présélections GitHub sont disponibles pour tous les types de référentiels.

Règles de triage automatique personnalisées sont disponibles pour les types de référentiels suivants :

  • Des référentiels publics sur GitHub.com
  • Référentiels appartenant à l’organisation sur GitHub Team ou GitHub Enterprise Cloud avec GitHub Code Security activé

Dans cet article

About Règles de triage automatique de Dependabot

Règles de triage automatique de Dependabot allow you to instruct Dependabot to automatically triage Dependabot alerts and Dependabot malware alerts. You can use Règles de triage automatique to:

  • Automatically dismiss or snooze certain alerts
  • Specify the Dependabot alerts you want Dependabot to open pull requests for

Rules are applied before alert notifications are sent, so enabling rules that auto-dismiss low-risk alerts will help reduce notification noise.

There are two types of Règles de triage automatique de Dependabot:

  • Présélections GitHub
  • Règles de triage automatique personnalisées

About Présélections GitHub

Présélections GitHub are rules curated by GitHub that are available for all repositories.

Dismiss low impact issues for development-scoped dependencies

La règle Dismiss low impact issues for development-scoped dependencies est une règle prédéfinie de GitHub qui rejette automatiquement certains types de vulnérabilités détectées dans des dépendances npm utilisées en phase de développement. These alerts cover cases that feel like false alarms to most developers as the associated vulnerabilities:

  • Are unlikely to be exploitable in a developer (non-production or runtime) environment.
  • May relate to resource management, programming and logic, and information disclosure issues.
  • At worst, have limited effects like slow builds or long-running tests.
  • Are not indicative of issues in production.

The rule is enabled by default for public repositories and can be opted into for private repositories. For instructions, see Enabling the Dismiss low impact issues for development-scoped dependencies rule for your private repository.

For more information about the criteria used by the rule, see Énumérateurs de failles courantes utilisés par les règles Dependabot prédéfinies de GitHub.

Dismiss package malware alerts

The Dismiss package malware alerts rule is a GitHub preset that auto-dismisses alerts that flag all versions of a package as malicious. If your project depends on an internal package with the same ecosystem and name as a malicious public package, Dependabot can generate a false positive alert, which the rule then auto-dismisses.

Important

Be aware that if a contributor adds a dependency that is truly malicious across all versions, this rule will auto-dismiss the related alert.

The Dismiss package malware alerts rule is disabled by default, but can be enabled for any repository using Dependabot malware alerts.

About Règles de triage automatique personnalisées

Remarque

Règles de triage automatique personnalisées pour Dependabot alerts sont disponibles sur les référentiels publics et sur tous les référentiels appartenant à l’organisation dans GitHub Team ou GitHub Enterprise avec GitHub Code Security activé.

With Règles de triage automatique personnalisées, you can create your own rules to automatically dismiss or reopen alerts based on targeted metadata, such as severity, package name, CWE, and more. You can also specify which Dependabot alerts you want Dependabot to open pull requests for. For more information, see Customizing auto-triage rules to prioritize Dependabot alerts.

You can create custom rules from the Settings tab of the repository, provided the repository belongs to an organization that has a license for GitHub Code Security or GitHub Advanced Security. For more information, see Adding custom auto-triage rules to your repository.

About auto-dismissing alerts

Whilst you may find it useful to use auto-triage rules to auto-dismiss alerts, you can still reopen auto-dismissed alerts and filter to see which alerts have been auto-dismissed. For more information, see Gestion des alertes qui ont été automatiquement ignorées par une règle de triage automatique de Dependabot.

Additionally, auto-dismissed alerts are still available for reporting and reviewing, and can be auto-reopened if the alert metadata changes, for example:

  • If you change the scope of a dependency from development to production.
  • If GitHub modifies certain metadata for the related advisory.

Auto-dismissed alerts are defined by the resolution:auto-dismiss close reason. Automatic dismissal activity is included in alert webhooks, REST and GraphQL APIs, and the audit log. For more information, see Points de terminaison d’API REST pour Dependabot alerts, and the "repository_vulnerability_alert" section in Examen du journal d’audit de votre organisation.

Next steps

To get started with Règles de triage automatique de Dependabot, see Using GitHub preset rules to prioritize Dependabot alerts.

To customize your auto-triage experience, see Customizing auto-triage rules to prioritize Dependabot alerts.