GitHub has security features that help keep code and secrets secure in repositories and across organizations. Some features are available for all repositories. Additional features are available to enterprises that use GitHub Advanced Security. For more information, see "About GitHub Advanced Security."
The GitHub Advisory Database contains a curated list of security vulnerabilities that you can view, search, and filter. For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database" in the GitHub.com documentation.
Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "Adding a security policy to your repository."
View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "About alerts for vulnerable dependencies."
The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
You can find the dependency graph on the Insights tab for your repository. For more information, see "About the dependency graph."
GitHub Advanced Security is available if your enterprise has a license for GitHub Advanced Security. It is restricted to repositories owned by an organization. For more information, see "About GitHub Advanced Security."
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."
Automatically detect tokens or credentials that have been checked into a repository. 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."
Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "About dependency review."