docs/content/github/administering-a-repository/about-securing-your-repository.md

title, intro, versions

title	intro	versions
About securing your repository	{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.	free-pro-team *

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

{% data variables.product.prodname_dotcom %} 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.

• Security policy

  Make it easy for people to confidentially report security vulnerabilities they've found in your repository. For more information, see "Adding a security policy to your repository."

• Security advisories

  Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage them to upgrade. For more information, see "About {% data variables.product.prodname_security_advisories %}."

• {% data variables.product.prodname_dependabot_alerts %} and security updates

  View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information, see "About alerts for vulnerable dependencies" and "About {% data variables.product.prodname_dependabot_security_updates %}."

• {% data variables.product.prodname_dependabot %} version updates

  Use {% data variables.product.prodname_dependabot %} 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 {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "About {% data variables.product.prodname_dependabot_version_updates %}."

• {% data variables.product.prodname_code_scanning_capc %} 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."

• Detected secrets

  View any secrets that {% data variables.product.prodname_dotcom %} 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."

Exploring dependencies

{% data variables.product.prodname_dotcom %}'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 {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities.

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