You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/concepts/supply-chain-security/about-dependabot-auto-triage-rules.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: About Dependabot auto-triage rules
3
-
intro: '{% data variables.dependabot.auto_triage_rules %} are a powerful tool to help you better manage your security alerts at scale. {% data variables.dependabot.github_presets %} are rules curated by {% data variables.product.company_short %} that you can use to filter out a substantial amount of false positives. {% data variables.dependabot.custom_rules_caps %} provide control over which alerts are ignored, snoozed, or trigger a {% data variables.product.prodname_dependabot %} security update to resolve the alert.'
3
+
intro: 'Control how {% data variables.product.prodname_dependabot %} handles security alerts, including filtering, ignoring, snoozing, or triggering security updates.'
4
4
product: '{% data reusables.gated-features.dependabot-auto-triage-rules %}'
5
5
versions:
6
6
fpt: '*'
@@ -35,9 +35,18 @@ There are two types of {% data variables.dependabot.auto_triage_rules %}:
35
35
> [!NOTE]
36
36
> {% data reusables.dependabot.dependabot-github-preset-auto-triage-rules %}
37
37
38
-
{% data variables.dependabot.github_presets %} are rules curated by {% data variables.product.company_short %}. {% data reusables.dependabot.dismiss-low-impact-rule %}
38
+
{% data variables.dependabot.github_presets %} are rules curated by {% data variables.product.company_short %}.
39
39
40
-
The rule is enabled by default for public repositories and can be opted into for private repositories. You can enable the rule for a private repository via the **Settings** tab for the repository. For more information, see [Enabling the `Dismiss low impact issues for development-scoped dependencies` rule for your private repository](/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts#enabling-the-dismiss-low-impact-issues-for-development-scoped-dependencies-rule-for-your-private-repository).
40
+
{% data reusables.dependabot.dismiss-low-impact-rule %} These alerts cover cases that feel like false alarms to most developers as the associated vulnerabilities:
41
+
42
+
* Are unlikely to be exploitable in a developer (non-production or runtime) environment.
43
+
* May relate to resource management, programming and logic, and information disclosure issues.
44
+
* At worst, have limited effects like slow builds or long-running tests.
45
+
* Are not indicative of issues in production.
46
+
47
+
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](/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts#enabling-the-dismiss-low-impact-issues-for-development-scoped-dependencies-rule-for-your-private-repository).
48
+
49
+
For more information about the criteria used by the rule, see [AUTOTITLE](/code-security/reference/supply-chain-security/criteria-for-preset-rules).
41
50
42
51
### About {% data variables.dependabot.custom_rules %}
title: Using GitHub preset rules to prioritize Dependabot alerts
3
-
intro: You can use {% data variables.dependabot.github_presets %}, which are rules curated by {% data variables.product.company_short %}, to auto-dismiss low impact development alerts for npm dependencies.
3
+
intro: Focus on alerts that matter by auto-dismissing low impact development alerts for npm dependencies.
4
4
permissions: '{% data reusables.permissions.dependabot-github-presets %}'
5
5
versions:
6
6
fpt: '*'
@@ -20,23 +20,9 @@ redirect_from:
20
20
contentType: how-tos
21
21
---
22
22
23
-
## About {% data variables.dependabot.github_presets %}
23
+
{% data reusables.dependabot.dismiss-low-impact-rule %} For more information about the rule, see [AUTOTITLE](/code-security/concepts/supply-chain-security/about-dependabot-auto-triage-rules#about-github-presets).
24
24
25
-
The `Dismiss low impact issues for development-scoped dependencies` rule is a {% data variables.product.company_short %} preset that auto-dismisses certain types of vulnerabilities that are found in npm dependencies used in development. These alerts cover cases that feel like false alarms to most developers as the associated vulnerabilities:
26
-
27
-
* Are unlikely to be exploitable in a developer (non-production or runtime) environment.
28
-
* May relate to resource management, programming and logic, and information disclosure issues.
29
-
* At worst, have limited effects like slow builds or long-running tests.
30
-
* Are not indicative of issues in production.
31
-
32
-
> [!NOTE]
33
-
> Automatic dismissal of low impact development alerts is currently only supported for npm.
34
-
35
-
The `Dismiss low impact issues for development-scoped dependencies` rule includes vulnerabilities relating to resource management, programming and logic, and information disclosure issues. For more information, see [Publicly disclosed CWEs used by the `Dismiss low impact issues for development-scoped dependencies` rule](#publicly-disclosed-cwes-used-by-the-dismiss-low-impact-issues-for-development-scoped-dependencies-rule).
36
-
37
-
Filtering out these low impact alerts allows you to focus on alerts that matter to you, without having to worry about missing potentially high-risk development-scoped alerts.
38
-
39
-
The `Dismiss low impact issues for development-scoped dependencies` rule is enabled by default on public repositories and disabled for private repositories. Administrators of private repositories can opt in by enabling the rule for their repository.
25
+
This rule is enabled by default on public repositories and disabled for private repositories. Administrators of private repositories can opt in by enabling the rule for their repository.
40
26
41
27
## Enabling the `Dismiss low impact issues for development-scoped dependencies` rule for your private repository
42
28
@@ -52,39 +38,3 @@ The `Dismiss low impact issues for development-scoped dependencies` rule is enab
52
38
1. Under "{% data variables.product.company_short %} presets", to the right of "Dismiss low impact issues for development-scoped dependencies", click {% octicon "pencil" aria-label="Edit rule" %}.
53
39
1. Under "State", select the dropdown menu, then click "Enabled".
54
40
1. Click **Save rule**.
55
-
56
-
## Publicly disclosed CWEs used by the `Dismiss low impact issues for development-scoped dependencies` rule
57
-
58
-
Along with the `ecosystem:npm` and `scope:development` alert metadata, we use the following {% data variables.product.company_short %}-curated Common Weakness Enumerations (CWEs) to filter out low impact alerts for the `Dismiss low impact issues for development-scoped dependencies` rule. We regularly improve this list and vulnerability patterns covered by built-in rules.
59
-
60
-
### Resource Management Issues
61
-
62
-
* CWE-400 Uncontrolled Resource Consumption
63
-
* CWE-770 Allocation of Resources Without Limits or Throttling
64
-
* CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
title: CWEs used by GitHub's preset Dependabot rules
3
+
intro: '{% data variables.product.github %} uses industry-standard criteria to help you filter {% data variables.product.prodname_dependabot_alerts %}.'
4
+
versions:
5
+
fpt: '*'
6
+
ghec: '*'
7
+
ghes: '*'
8
+
topics:
9
+
- Dependabot
10
+
- Version updates
11
+
- Repositories
12
+
- Dependencies
13
+
- Pull requests
14
+
shortTitle: Criteria for preset rules
15
+
contentType: reference
16
+
---
17
+
18
+
## `Dismiss low impact issues for development-scoped dependencies`
19
+
20
+
{% data reusables.dependabot.dismiss-low-impact-rule %}
21
+
22
+
Along with the `ecosystem:npm` and `scope:development` alert metadata, we use the following {% data variables.product.company_short %}-curated Common Weakness Enumerations (CWEs) to filter out low impact alerts for the `Dismiss low impact issues for development-scoped dependencies` rule. We regularly improve this list and vulnerability patterns covered by built-in rules.
23
+
24
+
### Resource Management Issues
25
+
26
+
* CWE-400 Uncontrolled Resource Consumption
27
+
* CWE-770 Allocation of Resources Without Limits or Throttling
28
+
* CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
The `Dismiss low impact issues for development-scoped dependencies` is a {% data variables.product.company_short %} preset rule. This rule auto-dismisses certain types of vulnerabilities that are found in npm dependencies used in development. The rule has been curated to reduce false positives and reduce alert fatigue. You cannot modify {% data variables.dependabot.github_presets %}. For more information about {% data variables.dependabot.github_presets %}, see [AUTOTITLE](/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts).
1
+
The `Dismiss low impact issues for development-scoped dependencies`rule is a {% data variables.product.company_short %} preset that auto-dismisses certain types of vulnerabilities that are found in npm dependencies used in development.
0 commit comments