English
No results found.

Explore by product

Repositories
  • Get started
  • Account and profile
  • Authentication
  • Repositories
  • GitHub
  • Enterprise administrators
  • Billing and payments
  • Organizations
  • Code security
  • GitHub Issues
  • GitHub Actions
  • GitHub Codespaces
  • GitHub Packages
  • Search on GitHub
  • Developers
  • REST API
  • GraphQL API
  • GitHub CLI
  • GitHub Discussions
  • GitHub Sponsors
  • Building communities
  • GitHub Pages
  • Education
  • GitHub Desktop
  • Atom
  • Electron
  • CodeQL
  • npm
    • English
  • English
  • 简体中文 (Simplified Chinese)
  • 日本語 (Japanese)
  • Español (Spanish)
  • Português do Brasil (Portuguese)

    • This version of GitHub Enterprise was discontinued on 2021-09-23. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

    In this article

    Exploring the dependencies of a repository

    Using the dependency graph, you can see the packages your project depends on. In addition, you can see any vulnerabilities detected in its dependencies.

    Viewing the dependency graph

    Enterprise owners must enable Dependabot alerts for vulnerable dependencies for your GitHub Enterprise Server instance before you can use this feature. For more information, see "Enabling the dependency graph and Dependabot alerts on your enterprise account."

    The dependency graph shows the dependencies of your repository. For information about the detection of dependencies and which ecosystems are supported, see "About the dependency 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 Dependency graph. Dependency graph tab in the left sidebar

    Dependencies view

    Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to Dependabot alerts.

    Dependencies graph

    Note: GitHub Enterprise Server does not populate the Dependents view.

    Troubleshooting the dependency graph

    If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.

    If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.