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/how-tos/secure-at-scale/configure-organization-security/index.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
-
title: Configure organization security
2
+
title: Configuring security features in your organization
3
+
shortTitle: Configure organization security
3
4
intro: Configure security across your organization by establishing coverage, managing settings, and controlling access to code security tools at scale.
Copy file name to clipboardExpand all lines: content/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/enabling-the-dependency-graph.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,11 @@
1
1
---
2
-
title: Configuring the dependency graph
2
+
title: Enabling the dependency graph
3
3
intro: You can allow users to identify their projects' dependencies by enabling the dependency graph.
4
4
permissions: '{% data reusables.permissions.dependency-graph %}'
{% data reusables.dependabot.about-the-dependency-graph %}
21
+
The dependency graph is a summary of the manifest and lock files stored in a repository and any dependencies that are submitted for the repository using the {% data variables.dependency-submission-api.name %}. For more information, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).
22
22
23
-
For more information, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).
23
+
When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, thegraph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
24
24
25
25
{% ifversion ghes %}
26
26
27
-
## Enabling the dependency graph
27
+
## Enabling the dependency graph for a {% data variables.product.prodname_ghe_server %} instance
28
28
29
29
{% data reusables.dependabot.ghes-enabling-dependency-graph %}
30
30
31
-
{% endif %}
31
+
{% else %}
32
32
33
-
{% ifversion fpt or ghec %}
33
+
## Enabling the dependency graph for a repository
34
34
35
-
## Configuring the dependency graph
35
+
Enabling the dependency graph gives {% data variables.product.github %} read-only access to the dependency manifest and lock files for a repository.
36
36
37
-
To generate a dependency graph, {% data variables.product.github %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph can be enabled or disabled for all repositories. For more information on viewing the dependency graph, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository).
37
+
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo-public-fork %}
38
38
39
-
{% data reusables.dependency-submission.dependency-submission-link %}
39
+
## Enabling the dependency graph for multiple repositories
40
40
41
-
### Enabling and disabling the dependency graph
41
+
You can enable or disable the dependency graph for all repositories owned by your user account, regardless of their visibility. See [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-security-and-analysis-settings-for-your-personal-account).
42
42
43
-
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo-public-fork %}
43
+
You can also enable the dependency graph for multiple repositories in an organization at the same time. For more information, see {% ifversion security-configurations %}[AUTOTITLE](/code-security/securing-your-organization).{% else %}[AUTOTITLE](/code-security/getting-started/quickstart-for-securing-your-organization).{% endif %}
44
44
45
45
{% endif %}
46
46
47
-
When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
47
+
## Next steps
48
+
49
+
{% data reusables.dependency-submission.dependency-submission-link %}
50
+
51
+
For more information on viewing the dependency graph, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository).
Copy file name to clipboardExpand all lines: data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo-public-fork.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,3 @@
1
-
Repository administrators can enable or disable the dependency graph for all repositories owned by your user account, regardless of their visibility. See [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-security-and-analysis-settings-for-your-personal-account).
2
-
3
-
You can also enable the dependency graph for multiple repositories in an organization at the same time. For more information, see {% ifversion security-configurations %}[AUTOTITLE](/code-security/securing-your-organization).{% else %}[AUTOTITLE](/code-security/getting-started/quickstart-for-securing-your-organization).{% endif %}
4
-
5
1
{% data reusables.repositories.navigate-to-repo %}
6
2
{% data reusables.repositories.sidebar-settings %}
7
3
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph. For more information, see [AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise).
1
+
If the dependency graph is not available on your {% data variables.product.prodname_ghe_server %} instance, ask an enterprise owner to enable it. For more information, see [AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise).
Additionally, you can use the {% data variables.dependency-submission-api.name %} to submit dependencies from the package manager or ecosystem of your choice, even if the ecosystem is not supported by dependency graph for manifest or lock file analysis.
1
+
You can use the {% data variables.dependency-submission-api.name %} to submit dependencies from the package manager or ecosystem of your choice, even if the ecosystem is not supported by dependency graph for manifest or lock file analysis.
2
2
Dependencies submitted to a project using the {% data variables.dependency-submission-api.name %} will show which detector was used for their submission and when they were submitted. For more information on the {% data variables.dependency-submission-api.name %}, see [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api).
0 commit comments