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 %}

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

{% endtip %}

{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}

1. In the left sidebar, click Network.

The{% ifversion repositories-forks-page-improvement %} forks page {% else %} Members graph {% endif %} lists the forks of a repository. {% ifversion repositories-forks-page-improvement %}For each fork, you can see:

• how many times the fork has been starred
• the number of direct forks (of the fork)
• the number of open issues
• the number of open pull requests
• when the fork was last updated (that is, the last push to any branch)
• when the fork was created

You can filter the list of forks to display active, inactive, starred, or archived forks, or to only display forks that have been updated within a specified time period (up to a period of five years). To view the most useful or most active forks, you can sort the list of forks by most starred forks or most recently updated forks, or by the number of open issues or open pull requests.

If you want to preserve the filters you have selected, you can save your filter and sort selections as the default so that any forks page you view, in any repository, will be filtered the same way.

{% else %}

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 {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.

{% endif %}

{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}

1. In the left sidebar, click Forks.

   

{% ifversion repositories-forks-page-improvement %}

1. Optionally, to filter the list to display forks updated within a specified time period, click Period, then choose a time period from the dropdown menu. For example, to see forks that have been updated within the last two years, choose "2 years" from the dropdown menu.

   

2. Optionally, to filter the list to only display active, inactive, starred, or archived forks, click Repository type, then choose one or multiple options from the dropdown menu. To clear a filter, click Repository type, then click the applied filter again to remove it.

   

3. Optionally, to sort the list by most starred forks, most recently updated forks, most open issues, or most open pull requests, click Sort, then choose an option from the dropdown menu.

   

4. Optionally, to preserve the filter values you have selected as the default filters for any time you view a forks page, click Save Defaults. If the currently selected filters are already the defaults, the button will be disabled and labeled as Defaults Saved.

   

{% endif %}

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 "AUTOTITLE" and "AUTOTITLE."

You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "AUTOTITLE."