{"meta":{"title":"保护存储库快速入门","intro":"管理对你的代码的访问。 自动查找和修复易受攻击的代码和依赖项。","product":"安全性和代码质量","breadcrumbs":[{"href":"/zh/enterprise-server@3.21/code-security","title":"安全性和代码质量"},{"href":"/zh/enterprise-server@3.21/code-security/getting-started","title":"入门"},{"href":"/zh/enterprise-server@3.21/code-security/getting-started/quickstart-for-securing-your-repository","title":"安全存储库快速入门"}],"documentType":"article"},"body":"# 保护存储库快速入门\n\n管理对你的代码的访问。 自动查找和修复易受攻击的代码和依赖项。\n\n\n## Introduction\n\nThis guide shows you how to configure security features for a repository.\n\nYour 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](/en/enterprise-server@3.21/code-security/getting-started/github-security-features).\n\nSome features are available for all repositories. Additional features are available to organizations and enterprises that use GitHub Secret Protection, GitHub Code Security, or GitHub Advanced Security. For more information, see [About GitHub Advanced Security](/en/enterprise-server@3.21/get-started/learning-about-github/about-github-advanced-security).\n\n## Managing access to your repository\n\nThe first step to securing a repository is to establish who can see and modify your code. For more information, see [Managing your repository's settings and features](/en/enterprise-server@3.21/repositories/managing-your-repositorys-settings-and-features).\n\nFrom the main page of your repository, click ** Settings**, then scroll down to the \"Danger Zone.\"\n\n* To change who can view your repository, click **Change visibility**. For more information, see [Setting repository visibility](/en/enterprise-server@3.21/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility).\n* To change who can access your repository and adjust permissions, click **Manage access**. For more information, see [Managing teams and people with access to your repository](/en/enterprise-server@3.21/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository).\n\n## Managing the dependency graph\n\nEnterprise owners can configure the dependency graph and Dependabot alerts for an enterprise. For more information, see [Enabling the dependency graph for your enterprise](/en/enterprise-server@3.21/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/enable-dependency-graph) and [Enabling Dependabot for your enterprise](/en/enterprise-server@3.21/admin/configuring-settings/configuring-github-connect/enabling-dependabot-for-your-enterprise).\n\nFor more information, see [Enabling the dependency graph](/en/enterprise-server@3.21/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/enable-dependency-graph).\n\n## Managing Dependabot alerts\n\nDependabot alerts are generated when GitHub identifies a dependency in the dependency graph with a vulnerability.\n\nAdditionally, you can use Dependabot auto-triage rules to manage your alerts at scale, so you can auto-dismiss or snooze alerts, and specify which alerts you want Dependabot to open pull requests for. For information about the different types of auto-triage rules, and whether your repositories are eligible, see [Dependabot auto-triage rules](/en/enterprise-server@3.21/code-security/concepts/supply-chain-security/dependabot-auto-triage-rules).\n\nFor an overview of the different features offered by Dependabot and instructions on how to get started, see [Dependabot quickstart guide](/en/enterprise-server@3.21/code-security/tutorials/secure-your-dependencies/dependabot-quickstart).\n\nEnterprise owners must configure the dependency graph and Dependabot alerts for an enterprise.\n\nOnce Dependabot alerts have been configured, repository administrators and organization owners can enable Dependabot alerts for private and internal repositories in their \"Advanced Security\" settings page. Public repositories are enabled by default. For more information, see [Enabling the dependency graph for your enterprise](/en/enterprise-server@3.21/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/enable-dependency-graph), [Enabling Dependabot for your enterprise](/en/enterprise-server@3.21/admin/configuring-settings/configuring-github-connect/enabling-dependabot-for-your-enterprise), and [Configuring Dependabot alerts](/en/enterprise-server@3.21/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-dependabot-alerts).\n\nFor more information, see [Dependabot alerts](/en/enterprise-server@3.21/code-security/concepts/supply-chain-security/dependabot-alerts).\n\n## Managing dependency review\n\nDependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see [Dependency review](/en/enterprise-server@3.21/code-security/concepts/supply-chain-security/dependency-review).\n\nDependency review is a GitHub Code Security feature.\n\nTo enable dependency review for a repository, ensure that the dependency graph is enabled.\n\n1. From the main page of your repository, click ** Settings**.\n2. Click **Advanced Security**.\n3. Check that dependency graph is configured for your enterprise.\n\n## Managing Dependabot security updates\n\nFor any repository that uses Dependabot alerts, you can enable Dependabot security updates to raise pull requests with security updates when vulnerabilities are detected.\n\n1. From the main page of your repository, click ** Settings**.\n2. Click **Advanced Security**.\n3. Next to Dependabot security updates, click **Enable**.\n\nFor more information, see [Dependabot security updates](/en/enterprise-server@3.21/code-security/concepts/supply-chain-security/dependabot-security-updates) and [Configuring Dependabot security updates](/en/enterprise-server@3.21/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-security-updates).\n\n## Managing Dependabot version updates\n\nYou can enable Dependabot to automatically raise pull requests to keep your dependencies up-to-date. For more information, see [Dependabot version updates](/en/enterprise-server@3.21/code-security/concepts/supply-chain-security/dependabot-version-updates).\n\nTo enable Dependabot version updates, you must create a `dependabot.yml` configuration file. For more information, see [Configuring Dependabot version updates](/en/enterprise-server@3.21/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-version-updates).\n\n## Configuring Code Security\n\nGitHub Code Security includes code scanning, CodeQL CLI and Copilot Autofix, as well as other features that find and fix vulnerabilities in your codebase.\n\nYou can configure code scanning to automatically identify vulnerabilities and errors in the code stored in your repository by using a CodeQL analysis workflow or third-party tool. Depending on the programming languages in your repository, you can configure code scanning with CodeQL using default setup, in which GitHub automatically determines the languages to scan, query suites to run, and events that will trigger a new scan. For more information, see [Configuring default setup for code scanning](/en/enterprise-server@3.21/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configure-code-scanning).\n\n1. From the main page of your repository, click ** Settings**.\n2. In the \"Security\" section of the sidebar, click ** Advanced Security**.\n3. If \"Code Security\" or \"GitHub Advanced Security\" is not already enabled, click **Enable**.\n4. To the right of \"CodeQL analysis\", select **Set up** , then click **Default**.\n5. In the pop-up window that appears, review the default configuration settings for your repository, then click **Enable CodeQL**.\n\nAs an alternative to default setup, you can use advanced setup, which generates a workflow file you can edit to customize your code scanning with CodeQL. For more information, see [Configuring advanced setup for code scanning](/en/enterprise-server@3.21/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning#configuring-advanced-setup-for-code-scanning-with-codeql).\n\n## Configuring Secret Protection\n\nGitHub Secret Protection includes secret scanning and push protection, as well as other features that help you detect and prevent secret leaks in your repository.\n\n1. From the main page of your repository, click ** Settings**.\n2. Click **Advanced Security**.\n3. If \"Secret Protection\" or \"GitHub Advanced Security\" is not already enabled, click **Enable**.\n4. If the option \"Secret scanning\" is shown, click **Enable**.\n5. Choose whether you want to enable additional features, such as scanning for generic patterns and push protection.\n\n## Setting a security policy\n\nIf you are a repository maintainer, it's good practice to specify a security policy for your repository by creating a file named `SECURITY.md` in the repository. This file instructs users about how to best contact you and collaborate with you when they want to report security vulnerabilities in your repository. You can view the security policy of a repository from the repository’s ** Security** tab.\n\n1. From the main page of your repository, click ** Security**.\n2. In the left sidebar, under \"Reporting\", click ** Security policy**.\n3. Click **Start setup**.\n4. Add information about supported versions of your project and how to report vulnerabilities.\n\nFor more information, see [Adding a security policy to your repository](/en/enterprise-server@3.21/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy).\n\n## Next steps\n\nYou can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see [Viewing and updating Dependabot alerts](/en/enterprise-server@3.21/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/view-dependabot-alerts), [Managing pull requests for dependency updates](/en/enterprise-server@3.21/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/manage-dependabot-prs), [Assessing code scanning alerts for your repository](/en/enterprise-server@3.21/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assess-alerts), and [Manage secret scanning alerts](/en/enterprise-server@3.21/code-security/how-tos/manage-security-alerts/manage-secret-scanning-alerts).\n\nYou can also use GitHub's tools to audit responses to security alerts. For more information, see [Auditing security alerts](/en/enterprise-server@3.21/code-security/concepts/security-at-scale/audit-security-alerts).\n\nIf you use GitHub Actions, you can use GitHub's security features to increase the security of your workflows. For more information, see [Secure use reference](/en/enterprise-server@3.21/actions/reference/security/secure-use)."}