Securing your repository

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 todos los repositorios. Las características adicionales se encuentran disponibles para las empresas que utilizan la GitHub Advanced Security. 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."

• To change who can view your repository, click Change visibility. For more information, see "Setting repository visibility."

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

Los propietarios de empresa pueden configurar las Las alertas del dependabot para una empresa. Para obtener más información, consulta la sección "Habilitar el Dependabot para tu empresa".

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.

Los propietarios de empresa pueden configurar las Las alertas del dependabot para una empresa. Para obtener más información, consulta la sección "Habilitar el Dependabot para tu empresa".

For more information, see "About Las alertas del dependabot."

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. To enable dependency review for a repository, ensure that the dependency graph is enabled and enable GitHub Advanced Security.

1. From the main page of your repository, click Settings.
2. Click Security & analysis.
3. Check that dependency graph is configured for your enterprise.
4. If GitHub Advanced Security is not already enabled, click Enable.

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 organization-owned repositories if your enterprise uses GitHub Advanced Security.

Configuring escaneo de secretos

Escaneo de secretos is available for organization-owned repositories if your enterprise uses GitHub Advanced Security. Escaneo de secretos may already be enabled for your repository, 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 "Managing escaneo de código for your repository," and "Managing alerts from escaneo de secretos."