Understanding connections between repositories

You can better understand the connections that exist between repositories by viewing a repository's network and forks and the projects that depend on the repository.

This repository insights graph is available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server.

Viewing a repository's network

The network graph displays the branch history of the entire repository network, including branches of the root repository and branches of forks that contain commits unique to the network.

Repository network graph

Tip: To see older branches, click and drag within the graph.

Accessing the network graph

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.
  2. Under your repository name, click Insights. Insights tab in the main repository navigation bar
  3. In the left sidebar, click Network. Network tab

Listing the forks of a repository

The Members graph displays all the forks of a repository.

Forks are listed alphabetically by the username of the person who forked the repository. You can click on the username to be redirected to the user's GitHub Enterprise Server profile page or click on the fork name to be redirected to the specific fork of the repository.

Repository members graph

Accessing the Members graph

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.
  2. Under your repository name, click Insights. Insights tab in the main repository navigation bar
  3. In the left sidebar, click Forks. Forks tab

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 alerts for vulnerable dependencies."

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.