Securing your repository

You can use a number of GitHub features to help keep your repository secure.

Repository administrators and organization owners can configure repository security settings.

Introduction

This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.

Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "GitHub security features."

Some security features are only available for public repositories, and for private repositories owned by organizations with an Advanced Security license. Para obtener más información, consulta la sección "Acerca de GitHub Advanced Security".

Managing access to your repository

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

From the main page of your repository, click Settings, then scroll down to the "Danger Zone."

Setting a security policy

  1. From the main page of your repository, click Security.
  2. Click Security policy.
  3. Click Start setup.
  4. Add information about supported versions of your project and how to report vulnerabilities.

For more information, see "Adding a security policy to your repository."

Managing the dependency graph

Once you have enabled the dependency graph, it is automatically generated for all public repositories, and you can choose to enable it for private repositories.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. Next to Dependency graph, click Enable or Disable.

For more information, see "Exploring the dependencies of a repository."

Managing Las alertas del dependabot

By default, GitHub detects vulnerabilities in public repositories and generates Las alertas del dependabot. Las alertas del dependabot can also be enabled for private repositories.

  1. Click your profile photo, then click Settings.
  2. Click Security & analysis.
  3. Click Enable all next to Las alertas del dependabot.

For more information, see "About alerts for vulnerable dependencies" and "Managing security and analysis settings for your user account."

Managing dependency review

Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories.Dependency review is available in all public repositories. For private and internal repositories you require a license for Advanced Security. To enable dependency review for a repository, enable the dependency graph and enable Advanced Security. For more information, see "About dependency review."

Managing Actualizaciones de seguridad del dependabot

For any repository that uses Las alertas del dependabot, you can enable Actualizaciones de seguridad del dependabot to raise pull requests with security updates when vulnerabilities are detected.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. Next to Actualizaciones de seguridad del dependabot, click Enable.

For more information, see "About Actualizaciones de seguridad del dependabot" and "Configuring Actualizaciones de seguridad del dependabot."

Managing Actualizaciones de versión del dependabot

You can enable Dependabot to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "About Actualizaciones de versión del dependabot."

To enable Actualizaciones de versión del dependabot, you must create a dependabot.yml configuration file. For more information, see "Enabling and disabling Dependabot version updates."

Configuring escaneo de código

Escaneo de código is available for all public repositories, and for private repositories owned by organizations with an Advanced Security license.

You can set up escaneo de código to automatically identify vulnerabilities and errors in the code stored in your repository by using a Flujo de trabajo de análisis de CodeQL or third-party tool. For more information, see "Setting up escaneo de código for a repository."

Configuring escaneo de secretos

Escaneo de secretos is available for all public repositories, and for private repositories owned by organizations with an Advanced Security license.

Escaneo de secretos may be enabled for your repository by default depending upon your organization's settings.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. If GitHub Advanced Security is not already enabled, click Enable.
  4. Next to Escaneo de secretos, click Enable.

Next steps

You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see "Viewing and updating vulnerable dependencies in your repository," "Managing pull requests for dependency updates," "Managing escaneo de código for your repository," and "Managing alerts from escaneo de secretos."

If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "About GitHub Security Advisories" and "Creating a security advisory."

¿Te ayudó este documento?

Política de privacidad

¡Ayúdanos a hacer geniales estos documentos!

Todos los documentos de GitHub son de código abierto. ¿Notas algo que esté mal o que no sea claro? Emite una solicitud de cambios.

Haz una contribución

O, aprende cómo contribuir.