About billing for GitHub Advanced Security

If you want to use GitHub Advanced Security features, you need a license.

GitHub Advanced Security is available for enterprise accounts on GitHub Enterprise Cloud and GitHub Enterprise Server. For more information, see "About GitHub's products."

关于 GitHub Advanced Security 的计费

您可以通过购买和上传 GitHub Advanced Security 许可为用户提供额外的代码安全功能。 有关 GitHub Advanced Security 的更多信息,请参阅“关于 GitHub Advanced Security”。

GitHub Advanced Security 的每个许可证都规定了可以使用这些功能的最大帐户或席位数量。 至少一个启用了该功能的仓库的每个活跃提交者将使用一个席位。 活跃的提交者是在过去 90 天内编写了至少一个被推送到仓库的提交的人。

To discuss licensing GitHub Advanced Security for your enterprise, contact GitHub' 销售团队.

关于 GitHub Advanced Security 的提交者数量

我们在 您的 GitHub Enterprise Server 实例上记录并显示 GitHub Advanced Security 的两个提交者:

  • 提交者是指参与组织中至少一个仓库并且占用企业许可中一个席位的提交者数量。 也就是说,他们也是组织成员、外部协作者,或者具有待处理的企业帐户中组织加入邀请。
  • 对此仓库/组织唯一是只参与该仓库或该组织中仓库的提交者数量。 此数字显示您可以通过禁用该仓库或组织的 GitHub Advanced Security 来释放多少许可证席位。

如果没有唯一的提交者,则意味着所有活跃的提交者也参与其他使用 GitHub Advanced Security 的仓库或组织。 禁用该仓库或组织的功能将不会在您的许可证上腾出任何席位。

从企业帐户中删除用户后,用户的许可证在 24 小时内被释放。

注:用户可以参与多个仓库或组织。 使用数是在整个企业帐户中计量的,确保每个成员使用一个席位,无论该用户参与多少个仓库或组织。

为仓库启用或禁用 Advanced Security 时,GitHub 将显示许可证使用情况变化的概况。 如果您禁用对 GitHub Advanced Security 的访问,任何被“唯一”提交者使用的席位都将释放。

如果您超过了许可证限制,GitHub Advanced Security 将继续在所有已启用的仓库中工作。 但是,在为新仓库启用 GitHub Advanced Security 的组织中,将会创建禁用该功能的仓库。 此外,对现有仓库启用 GitHub Advanced Security 的选项将不可用。

一旦您释放一些席位,通过对某些仓库禁用 GitHub Advanced Security 或通过增加您的许可证大小,用于启用 GitHub Advanced Security 的选项将继续正常工作。

您可以执行策略以允许或不允许企业帐户拥有的组织使用 Advanced Security。 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."

Calculating committer spending

The following example timeline demonstrates the events during a month that affect billing for GitHub Advanced Security in an enterprise. For each month, you will find events, the total committer count, and the total number of committers that GitHub would bill for.

日期 Events during the month Total committer count Committers billed for the month
August 1 A member of your enterprise enables GitHub Advanced Security for repository X. Repository X has 50 committers over the past 90 days. 50 50
September 5 Developer A leaves the team working on repository X. Developer A's contributions continue to count for 90 days. 50 50
September 8 Developer B pushes a commit to repository X for the first time. Developer B's usage is pro-rated, because the developer began contributing to repository X partway through the month. _50 + 1_
51
_50 + 0.8_
50.8
October and November Developer A's contributions to repository X continue to count because the contributions were within the past 90 days. GitHub now bills for developer B for the entire month because developer B now has contributions within the past 90 days. 51 51
December 4 90 days have passed since developer A's last contribution to repository _X. The 90 days lapsed after December started, so GitHub bills for developer A for the entire month. _51 - 1_
50

51
December 11 Developer C joins the company and pushes a commit to repository X for the first time. Developer C's usage is pro-rated at 70% for 21 out of 30 days. _50 + 1_
51
_51 + .07_
51.7
January GitHub no longer bills for developer A. GitHub bills for developer C for the entire month. 51 51
February 15 A member of your enterprise disables GitHub Advanced Security for repository X. The 51 contributors to repository X do not work in any other repositories with GitHub Advanced Security. GitHub bills for the developers' usage in repository X for February. _51 - 51_
0

51
March No repository owned by your enterprise has GitHub Advanced Security enabled. 0 0

Getting the most out of GitHub Advanced Security

当您决定哪些仓库和组织优先用于 GitHub Advanced Security 时,应该查看它们并识别:

  • 对公司成功至关重要的代码库。 在这些项目中,引入了易受攻击代码、硬编码的密钥或易受攻击的依赖项,将对您的公司将产生最大的影响。
  • 提交频率最高的代码库。 这些是最积极开发的项目,因此出现安全问题的风险较高。

When you have enabled GitHub Advanced Security for these organizations or repositories, assess which other codebases you could add without incurring billing for unique committers. Finally, review the remaining important and busy codebases. If you want to increase the number of seats in your license, contact GitHub' 销售团队.

此文档对您有帮助吗?

隐私政策

帮助我们创建出色的文档!

所有 GitHub 文档都是开源的。看到错误或不清楚的内容了吗?提交拉取请求。

做出贡献

或, 了解如何参与。