About alerts for vulnerable dependencies

GitHub Enterprise Server sends Alertas do Dependabot when we detect vulnerabilities affecting your repository.

About vulnerable dependencies

Uma vulnerabilidade é um problema no código de um projeto que poderia ser explorada para corromper a confidencialidade, a integridade ou a disponibilidade do projeto ou de outros projetos que usam o código. As vulnerabilidades variam de tipo, gravidade e método de ataque.

When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.

Detection of vulnerable dependencies

Dependabot detects vulnerable dependencies and sends Alertas do Dependabot when:

Além disso, GitHub pode revisar todas as dependências adicionadas, atualizadas ou removidas em um pull request feita para o branch padrão de um repositório e sinalizar quaisquer alterações que introduziriam uma vulnerabilidade no seu projeto. Isso permite que você detecte e gerencie as dependências vulneráveis antes, e não depois, de elas alcançarem seu código. Para obter mais informações, consulte "Revisar as mudanças de dependências em um pull request".

For a list of the ecosystems that GitHub Enterprise Server can detect vulnerabilities and dependencies for, see "Supported package ecosystems."

Note: It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.

Alertas do Dependabot for vulnerable dependencies

Enterprise owners must enable Alertas do Dependabot for vulnerable dependencies for your GitHub Enterprise Server instance before you can use this feature. Para obter mais informações, consulteHabilitando o gráfico de dependências e Alertas do Dependabot na sua conta corporativa."

When GitHub Enterprise Server identifies a vulnerable dependency, we generate a Dependabot alert and display it on the Security tab for the repository and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version. GitHub Enterprise Server may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "Configuring notifications for vulnerable dependencies."

Note: GitHub Enterprise Server's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.

Access to Alertas do Dependabot

You can see all of the alerts that affect a particular project in the repository's dependency graph. For more information, see "Viewing and updating vulnerable dependencies in your repository."

By default, we notify people with admin permissions in the affected repositories about new Alertas do Dependabot.

To receive notifications about Alertas do Dependabot on repositories, you need to watch these repositories, and subscribe to receive "All Activity" notifications or configure custom settings to include "Security alerts." For more information, see "Configuring your watch settings for an individual repository."

You can choose the delivery method for notifications, as well as the frequency at which the notifications are sent to you. For more information, see "Configuring notifications for vulnerable dependencies."

You can also see all the Alertas do Dependabot that correspond to a particular vulnerability in the Banco de Dados Consultivo GitHub. For more information about advisory data, see "Browsing security vulnerabilities in the Banco de Dados Consultivo GitHub" in the GitHub.com documentation.

Esse documento ajudou você?

Política de Privacidade

Ajude-nos a tornar esses documentos ótimos!

Todos os documentos do GitHub são de código aberto. Você percebeu que algo que está errado ou não está claro? Envie um pull request.

Faça uma contribuição

Ou, aprenda como contribuir.