You can make extra features for code security available to users by buying and uploading a license for GitHub Advanced Security. For more information about GitHub Advanced Security, see "About GitHub Advanced Security."
GitHub Advanced Security 的每个许可证都规定了可以使用这些功能的最大帐户或席位数量。 至少一个启用了该功能的仓库的每个活跃提交者将使用一个席位。 如果提交者的某个提交在过去 90 天内被推送到存储库，则无论其最初创建时间如何，都将被视为活动提交者。
注意： 活动提交者是使用提交作者信息和将代码推送到 GitHub Enterprise Server 时的时间戳计算的。
当用户将代码推送到 GitHub 时，在该推送中编写代码的每个用户都会计入 GitHub Advanced Security 席位，即使代码不是 GitHub 的新代码。
用户应始终从最近的基本分支创建分支，或在推送之前变基。 这将确保在过去 90 天内未提交的用户不会占用 GitHub Advanced Security 席位。
To discuss licensing GitHub Advanced Security for your enterprise, contact GitHub' 销售团队.
We record and display two numbers of committers for GitHub Advanced Security on 您的 GitHub Enterprise Server 实例:
- Committers is the number of committers who contributed to at least one repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
- Unique to this repository/organization is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling GitHub Advanced Security for that repository or organization.
If there are no unique committers, all active committers also contribute to other repositories or organizations that use GitHub Advanced Security. Disabling the feature for that repository or organization would not free any seats on your license.
When you remove a user from your enterprise account, the user's license is freed within 24 hours.
Note: Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
为仓库启用或禁用 Advanced Security 时，GitHub 将显示许可证使用情况变化的概况。 如果您禁用对 GitHub Advanced Security 的访问，任何被“唯一”提交者使用的席位都将释放。
如果您超过了许可证限制，GitHub Advanced Security 将继续在所有已启用的仓库中工作。 但是，在为新仓库启用 GitHub Advanced Security 的组织中，将会创建禁用该功能的仓库。 此外，对现有仓库启用 GitHub Advanced Security 的选项将不可用。
一旦您释放一些席位，通过对某些仓库禁用 GitHub Advanced Security 或通过增加您的许可证大小，用于启用 GitHub Advanced Security 的选项将继续正常工作。
You can enforce policies to allow or disallow the use of Advanced Security by organizations owned by your enterprise account. For more information, see "Enforcing policies for Advanced Security in your enterprise."
For more information on viewing license usage, see "Viewing your GitHub Advanced Security usage."
The following example timeline demonstrates how active committer count for GitHub Advanced Security could change over time in an enterprise. For each month, you will find events, along with the resulting committer count.
|Date||Events during the month||Total committers|
|A member of your enterprise enables GitHub Advanced Security for repository X. Repository X has 50 committers over the past 90 days.||50|
|Developer A leaves the team working on repository X. Developer A's contributions continue to count for 90 days.||50|
|Developer A's contributions no longer count towards the licences required, because 90 days have passed.||50 - 1|
|A member of your enterprise enables GitHub Advanced Security for a second repository, repository Y. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo X and do not require additional licenses.||49 + 10|
|A member of your enterprise disables GitHub Advanced Security for repository X. Of the 49 developers who were working on repository X, 10 still also work on repository Y, which has a total of 20 developers contributing in the last 90 days.||49 - 29|
Note: A user will be flagged as active when their commits are pushed to any branch of a repository, even if the commits were authored more than 90 days ago.
当您决定哪些仓库和组织优先用于 GitHub Advanced Security 时，应该查看它们并识别：
- 对公司成功至关重要的代码库。 These are the projects for which the introduction of vulnerable code, hard-coded secrets, or insecure dependencies would have the greatest impact on your company.
- 提交频率最高的代码库。 这些是最积极开发的项目，因此出现安全问题的风险较高。
对这些组织或仓库启用 GitHub Advanced Security 后，评估您可以添加哪些其他代码库，而不会对唯一提交者产生计费。 最后，查看其余重要和繁忙的代码库。 如果您想增加许可证中的席位数，请联系 GitHub' 销售团队。