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/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ Each alert highlights a problem with the code and the name of the tool that iden
50
50
51
51
{% data reusables.code-scanning.alert-default-branch %}
52
52
53
-

53
+

54
54
55
55
If you configure {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ You can use more than one issue to track the same {% data variables.product.prod
32
32
33
33
* The {% data variables.product.prodname_code_scanning %} alerts list page will show which alerts are tracked in issues so that you can view at a glance which alerts still require processing and how many issues they are tracked in.
34
34
35
-

35
+

36
36
37
37
* A "tracked in" section will also show in the corresponding alert page.
38
38
@@ -45,7 +45,7 @@ You can use more than one issue to track the same {% data variables.product.prod
45
45
46
46
The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
47
47
48
-

48
+

49
49
50
50
The status of the tracked alert won't change if you change the checkbox state of the corresponding task list item (checked/unchecked) in the issue.
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@ When {% data variables.product.prodname_copilot_autofix_short %} is enabled for
133
133
134
134
Usually, when you suggest changes to a pull request, your comment contains changes for a single file that is changed in the pull request. The following screenshot shows an {% data variables.product.prodname_copilot_autofix_short %} comment that suggests changes to the `index.js` file where the alert is displayed. Since the potential fix requires a new dependency on `escape-html`, the comment also suggests adding this dependency to the `package.json` file, even though the original pull request makes no changes to this file.
135
135
136
-

136
+

137
137
138
138
### Assessing and committing an {% data variables.product.prodname_copilot_autofix_short %} suggestion
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ If you are on a free, pro, or team plan, you can only use {% data variables.prod
39
39
1. If there is an associated and active **Enable** button, {% data variables.product.prodname_GH_advanced_security %} is available for this repository but not yet enabled.
40
40
1. If use of {% data variables.product.prodname_GH_advanced_security %} is blocked by a policy, the **Enable** button is inactive and the owner of the policy is listed.
41
41
42
-

42
+

Copy file name to clipboardexpand all lines: content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -61,11 +61,11 @@ This section uses an open source Java project called "sofa-jraft" as an example.
61
61
62
62
1. Display the {% data variables.product.prodname_codeql %} model editor. By default the editor runs in application mode, so the list of external APIs used by the selected codebase is shown.
63
63
64
-

64
+

65
65
66
66
1. Click to expand an external API and view the list of calls from the codebase to the external dependency.
67
67
68
-

68
+

69
69
70
70
1. Click **View** associated with an API call or method to show where it is used in your codebase.
71
71
@@ -104,13 +104,13 @@ This section uses an open source Java project called "sofa-jraft" as an example.
104
104
105
105
1. Display the {% data variables.product.prodname_codeql %} model editor. By default the editor runs in application mode. Click **Model as dependency** to display dependency mode. The screen changes to show the public API of the framework or library.
106
106
107
-

107
+

108
108
109
109
1. Click to expand a package and view the list of available methods.
110
110
111
111
1. Click **View** associated with a method to show its definition.
112
112
113
-

113
+

114
114
115
115
1. When you have determined how to model the method, define the "Model type".
116
116
@@ -141,7 +141,7 @@ The editor will create a separate model file for each package that you model.
141
141
142
142
Some methods support more than one data flow. It is important to model all the data flows for a method, otherwise you cannot detect all the potential problems associated with using the method. First you model one data flow for the method, and then use the **+** button in the method row to specify a second data flow model.
143
143
144
-

144
+

145
145
146
146
## Testing {% data variables.product.prodname_codeql %} model packs in {% data variables.product.prodname_vscode_shortname %}
Copy file name to clipboardexpand all lines: content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ You can configure notification settings for yourself or your organization from t
48
48
{% data reusables.notifications.vulnerable-dependency-notification-options %}
49
49
50
50
{% ifversion update-notification-settings-22 %}
51
-
{% endif %}{% ifversion ghes %}
51
+
{% endif %}{% ifversion ghes %}
52
52
{% endif %}
Copy file name to clipboardexpand all lines: content/code-security/getting-started/quickstart-for-securing-your-organization.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ You can choose to enable a security feature automatically in all new repositorie
104
104
1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
105
105
1. Below the name of the feature, select the option for automatically enabling the feature in applicable future repositories.
106
106
107
-

107
+

Copy file name to clipboardexpand all lines: content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ In addition to displaying an alert in the **Security** tab of the repository, {%
34
34
1. On your notification settings page, under "Subscriptions", then under "Watching", select the **Notify me** dropdown.
35
35
1. Select "Email" as a notification option, then click **Save**.
36
36
37
-

37
+

Copy file name to clipboardexpand all lines: content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the
56
56
* High entropy random strings
57
57
* A 32-bit checksum
58
58
59
-

59
+

60
60
61
61
* A test account for your service. This will allow us to generate and analyze examples of the secrets, further reducing false positives.
62
62
* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. The URL doesn't have to be unique for each secret type.
Copy file name to clipboardexpand all lines: content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ For examples showing how affected versions are defined in some existing advisori
105
105
106
106
* You cannot specify multiple affected version ranges in the same field, such as `> 2.0, < 2.3, > 3.0, < 3.2`.To specify more than one range, you must create a new **Affected products** section for each range, by clicking the **+ Add another affected product** button.
107
107
108
-

108
+

109
109
* If the affected version range includes only a single upper or lower bound:
110
110
* The implicit value is always `> 0` if the lower bound is not explicitly specified.
111
111
* The implicit value is always infinity if the upper bound is not explicitly specified.
Copy file name to clipboardexpand all lines: content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ To keep information about vulnerabilities secure, integrations, including CI, ca
37
37
1. In the "Security Advisories" list, click the name of the security advisory you'd like to create a temporary private fork in.
38
38
1. Scroll to the bottom of the advisory form and click **Start a temporary private fork**.
39
39
40
-

40
+

41
41
42
42
A private fork of the repository is created and shown on the advisory page.
Copy file name to clipboardexpand all lines: content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ The instructions in this article refer to enablement at repository level. For in
31
31
{% data reusables.repositories.sidebar-settings %}
32
32
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
33
33
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
34
-

34
+

35
35
36
36
{% data reusables.security-advisory.private-vulnerability-reporting-security-researcher %}
37
37
@@ -56,6 +56,6 @@ Notifications depend on the user's notification preferences. You will receive an
56
56
1. On your notification settings page, under "Subscriptions," then under "Watching," select the **Notify me** dropdown.
57
57
1. Select "Email" as a notification option, then click **Save**.
58
58
59
-

59
+

Copy file name to clipboardexpand all lines: content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
70
70
1. In the "Security Advisories" list, click the name of the security advisory you'd like to publish.
71
71
1. Scroll to the bottom of the advisory form and click **Publish advisory**.
72
72
73
-

73
+

74
74
75
75
> [!NOTE]
76
76
> If you selected "Request CVE ID later", you will see a **Request CVE** button in place of the **Publish advisory** button. For more information, see [Requesting a CVE identification number (Optional)](#requesting-a-cve-identification-number-optional) below.
@@ -89,7 +89,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
89
89
1. In the "Security Advisories" list, click the name of the security advisory you'd like to request a CVE identification number for.
90
90
1. Scroll to the bottom of the advisory form and click **Request CVE**.
91
91
92
-

92
+

Copy file name to clipboardexpand all lines: content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ You may notice some repositories have a "Used by" section in the sidebar of the
91
91
92
92
The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
93
93
94
-

94
+

95
95
96
96
Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
0 commit comments