About securing your repository

GitHub Enterprise Server provides a number of ways that you can help keep your repository secure.

In this article

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 for all repositories

Available with Advanced Security

These features are available if you have an Advanced Security license. For more information, see "About GitHub Advanced Security."

  • Code scanning 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 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."

Exploring dependencies

GitHub'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 GitHub can generate 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."

Did this doc help you?

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

Or, learn how to contribute.