Viewing a repository's network
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
Tip: To see older branches, click and drag within the graph.
Accessing the network graph
- On your enterprise, navigate to the main page of the repository.
- Under your repository name, click Insights.
- In the left sidebar, click Network.
Listing the forks of a repository
The Members graph lists the forks of a repository.
Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's GitHub AE profile page or click on the fork name to be redirected to the specific fork of the repository.
Accessing the Members graph
On your enterprise, navigate to the main page of the repository.
Under your repository name, click Insights.
In the left sidebar, click Forks.
Viewing the dependencies of a repository
You can use the dependency graph to explore the code your repository depends on.
Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "About the dependency graph" and "Exploring the dependencies of a repository."
You can also set up your repository so that GitHub alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "About Dependabot alerts."