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. 詳しい情報については、「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 advisories 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."
Note: Dependabotアラート is currently in beta and is subject to change.
View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "About Dependabotアラート."
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."
For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled.
GitHub Advanced Security features are available for repositories owned by an organization. 詳しい情報については、「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. You can view alerts for any secrets that GitHub finds in your code, so that you know which tokens or credentials to treat 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."
Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "About the security overview."