About Правила автообработки зависимостей
Правила автообработки зависимостей allow you to instruct Dependabot to automatically triage Dependabot alerts and Dependabot malware alerts. You can use Правила автоматической сортировки 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 Правила автообработки зависимостей:
- Предустановки GitHub
- Пользовательские правила автоматической сортировки
About Предустановки GitHub
Предустановки GitHub are rules curated by GitHub that are available for all repositories.
Dismiss low impact issues for development-scoped dependencies
Dismiss low impact issues for development-scoped dependencies Правило — это предустановка GitHub, которая автоматически закрывает определенные типы уязвимостей, обнаруженных в зависимостях npm, используемых в разработке. 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 CWE, используемые в предустановленных правилах Dependabot на 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.
Внимание
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 пользовательские правила автоматической сортировки
Примечание.
Пользовательские правила автоматической сортировки для Dependabot alerts доступны в общедоступных репозиториях и на всех репозиториях, принадлежащих организации, в GitHub Team или GitHub Enterprise с включенной функцией GitHub Code Security .
With пользовательские правила автоматической сортировки, 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 Управление оповещениями, которые были автоматически отклонены правилом auto-triage 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 Конечные точки REST API для Dependabot alerts, and the "repository_vulnerability_alert" section in Просмотр журнала аудита для вашей организации.
Next steps
To get started with Правила автообработки зависимостей, see Using GitHub preset rules to prioritize Dependabot alerts.
To customize your auto-triage experience, see Customizing auto-triage rules to prioritize Dependabot alerts.