Skip to main content
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.

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

Algunas características están disponibles para los repositorios en todos los planes. Las características adicionales se encuentran disponibles para las empresas que utilizan la GitHub Advanced Security. Las características de la GitHub Advanced Security también se habilitan para todos los repositorios públicos de GitHub.com. 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

The dependency graph is automatically generated for all public repositories, and you can choose to enable it for private repositories. It interprets manifest and lock files in a repository to identify dependencies.

  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

Las alertas del dependabot are generated when GitHub identifies a dependency in the dependency graph with a vulnerability. You can enable Las alertas del dependabot for any repository.

  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 Las alertas del dependabot" and "Managing security and analysis settings for your personal account."

Managing dependency review

Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "About dependency review."

Dependency review is a GitHub Advanced Security feature. Dependency review is already enabled for all public repositories. Organizations that use Nube de GitHub Enterprise with Advanced Security can additionally enable dependency review for private and internal repositories. For more information, see the Nube de GitHub Enterprise documentation.

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 "Configuring Dependabot version updates."

Configuring escaneo de código

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

Escaneo de código is available for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for GitHub Advanced Security.

Configuring escaneo de secretos

Escaneo de secretos is enabled for all public repositories and is available for private repositories owned by organizations that are part of an enterprise with a license for GitHub Advanced Security. For more information, see the Nube de GitHub Enterprise documentation.

Next steps

You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see "Viewing Las alertas del dependabot for vulnerable dependencies," "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."