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.
GitHub AE is currently under limited release. Please contact our Sales Team to find out more.

About securing your repository

GitHub Enterprise 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 with 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

    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."

¿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.