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.
GitHub Enterprise detects vulnerable dependencies and sends security alerts when:
- New advisory data is synchronized to GitHub Enterprise Server each hour from GitHub.com. For more information about advisory data, see "Browsing security vulnerabilities in the Banco de Dados Consultivo GitHub."
- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "About the dependency graph."
For a list of the ecosystems that GitHub Enterprise 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.
O seu administrador do site deve habilitar alertas de segurança para dependências vulneráveis para sua instância do GitHub Enterprise Server antes de você poder usar este recurso. Para obter mais informações, consulte "Habilitar alertas para dependências vulneráveis em GitHub Enterprise Server".
When GitHub Enterprise identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
Note: GitHub Enterprise's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and alert you with our most up-to-date information, we will not be able to catch everything or alert you to 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.
You can see all of the alerts that affect a particular project in the repository's dependency graph.
We send security alerts to people with admin permissions in the affected repositories by default. GitHub Enterprise never publicly discloses identified vulnerabilities for any repository.
By default, if your site administrator has configured email for notifications on your instance, you will receive security alerts by email. You can also choose to receive security alerts in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the GitHub Enterprise user interface. For more information, see "Choosing the delivery method for your notifications ."