Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

About securing your repository

GitHub provides a number of ways that you can help keep your repository secure.

En este artículo

Setting up your repository securely

The first step to securing a repository is to set up who can see and modify your code. For more information, see "Managing repository settings."

Securing your repository

GitHub has a growing set of security features that help you keep your code secure. You can find these on the Security tab for your repository.

Available for all repositories

  • Dependabot de GitHub version updates

    Use Dependabot de GitHub to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for Actualizaciones de seguridad del Dependabot de GitHub to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "About Actualizaciones de versión para el Dependabot de GitHub."

Available for public repositories and for repositories with Advanced Security

These features are available for all public repositories, and for private repositories owned by organizations with an Advanced Security license. For more information, see "About GitHub Advanced Security."

  • Escaneo de código alerts

    Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "About code scanning."

  • Escaneo de secretos alerts

    For private repositories, view any secrets that GitHub has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "About secret scanning."

  • Dependency review - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "About dependency review."

Exploring dependencies

GitHub's dependency graph allows you to explore:

  • Ecosystems and packages that your repository depends on
  • Repositories and packages that depend on your repository

You must enable the dependency graph before GitHub can generate Alertas del Dependabot de GitHub for dependencies with security vulnerabilities. Enabling the dependency graph also enables GitHub to run dependency reviews of pull requests.

You can find the dependency graph on the Insights tab for your repository. For more information, see "About the dependency graph."

¿Te ayudó este documento?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.