Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco.
Versão do artigo: Enterprise Server 2.19

Sobre o gráfico de dependências

Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.

Neste artigo

Dependency graph availability

The dependency graph is available for every repository that defines dependencies in a supported package ecosystem using a supported file format.

Your site administrator must enable security alerts for vulnerable dependencies for sua instância do GitHub Enterprise Server before you can use this feature. For more information, see "Enabling security alerts for vulnerable dependencies on GitHub Enterprise Server."

Sobre o gráfico de dependências

The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows dependencies, that is, the ecosystems and packages it depends on. GitHub Enterprise Server does not calculate information about dependents, the repositories and packages that depend on a repository.

When you push a commit to GitHub Enterprise that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated. For information on the supported ecosystems and manifest files, see "Supported package ecosystems" below.

Dependencies included

The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:

  • Direct dependencies, that are explicitly defined in a manifest or lock file
  • Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies

The dependency graph identifies indirect dependencies from the lock files.

Using the dependency graph

You can use the dependency graph to:

Enabling the dependency graph

If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. Para obter mais informações, consulte "Habilitar alertas de segurança para dependências vulneráveis no GitHub Enterprise Server".

When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Once enabled, the graph is automatically updated with every push to the repository.

Supported package ecosystems

The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.

Gerenciador de pacotesLinguagemFormatos recomendadosAll supported formats
ComposerPHPcomposer.lock
dotnet CLI.NET languages (C#, C++, F#, VB).csproj, .vbproj, .nuspec, .vcxproj, .fsproj.csproj, .vbproj, .nuspec, .vcxproj, .fsproj, packages.config
MavenJava, Scalapom.xmlpom.xml
npmJavaScriptpackage-lock.jsonpackage-lock.json, package.json
Python PIPPythonrequirements.txt, pipfile.lockrequirements.txt, pipfile.lock, setup.py*
RubyGemsRubyGemfile.lockGemfile.lock, Gemfile, *.gemspec
YarnJavaScriptyarn.lockpackage.json, yarn.lock

Note: If you list your Python dependencies within a setup.py file, we may not be able to parse and list every dependency in your project.

Leia mais

Pergunte a uma pessoa

Não consegue encontrar o que procura?

Entrar em contato