К основному содержимому

docs.github.com

На контроле

GitHub Bug Bounty Program Legal Safe Harbor - GitHub Docs

С 18 сентября 2026 без изменений — оферта выглядит стабильной.

Исходная оферта

Открыть оригинал на docs.github.com

https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor

Какие ещё документы есть у github.com?

У компании в каталоге есть и другие оферты — их история ведётся так же.

Все оферты github.com

Откуда этот документ и когда его проверяли?

Сайт-источник
docs.github.com
Первая фиксация
Последняя проверка
Версий в архиве
13 версий
Зафиксировано изменений
1 изменение
Периодичность проверки
6 часов

Насколько сильно меняли эту оферту?

Каждая строка — одна зафиксированная правка. Пункт считается изменённым, если его текст стал другим; добавленные и удалённые считаются отдельно.

Правки оферты «GitHub Bug Bounty Program Legal Safe Harbor - GitHub Docs»: дата, сколько пунктов изменено, сколько появилось новых и сколько убрано
Дата правки Пунктов изменено Новых пунктов Убрано пунктов
0 3 0

In this article GitHub Bug Bounty Program Legal Safe Harbor Copy markdown In this article Summary We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with...

Раскрыть документ

In this article

GitHub Bug Bounty Program Legal Safe Harbor

Copy markdown

In this article

Summary

  • We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with our bug bounty policy. We cannot bind any third party, so do not assume this protection extends to any third party. If in doubt, ask us before engaging in any specific action you think might go outside the bounds of our policy.

  • Because both identifying and non-identifying information can put a researcher at risk, we limit what we share with third parties. We may provide non-identifying substantive information from your report to an affected third party, but only after notifying you and receiving a commitment that the third party will not pursue legal action against you. We will only share identifying information (name, email address, phone number, etc.) with a third party if you give your written permission.

  • If your security research as part of the bug bounty program violates certain restrictions in our site policies, the safe harbor terms permit a limited exemption.

1. Safe Harbor Terms

To encourage research and coordinated disclosure of security vulnerabilities, we will not pursue civil or criminal action, or send notice to law enforcement for accidental or good faith violations of this policy. We consider security research and vulnerability disclosure activities conducted consistent with this policy to be “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and other applicable computer use laws such as Cal. Penal Code 502(c). We waive any potential DMCA claim against you for circumventing the technological measures we have used to protect the applications in this bug bounty program's scope.

Please understand that if your security research involves the networks, systems, information, applications, products, or services of a third party (which is not us), we cannot bind that third party, and they may pursue legal action or law enforcement notice. We cannot and do not authorize security research in the name of other entities, and cannot in any way offer to defend, indemnify, or otherwise protect you from any third party action based on your actions.

You are expected, as always, to comply with all laws applicable to you, and not to disrupt or compromise any data beyond what this bug bounty program permits.

Please contact us before engaging in conduct that may be inconsistent with or unaddressed by this policy. We reserve the sole right to make the determination of whether a violation of this policy is accidental or in good faith, and proactive contact to us before engaging in any action is a significant factor in that decision. If in doubt, ask us first!

2. Third Party Safe Harbor

If you submit a report through our bug bounty program which affects a third party service, we will limit what we share with any affected third party. We may share non-identifying content from your report with an affected third party, but only after notifying you that we intend to do so and getting the third party's written commitment that they will not pursue legal action against you or initiate contact with law enforcement based on your report. We will not share your identifying information with any affected third party without first getting your written permission to do so.

Please note that we cannot authorize out-of-scope testing in the name of third parties, and such testing is beyond the scope of our policy. Refer to that third party's bug bounty policy, if they have one, or contact the third party either directly or through a legal representative before initiating any testing on that third party or their services. This is not, and should not be understood as, any agreement on our part to defend, indemnify, or otherwise protect you from any third party action based on your actions.

Это начало документа. Читать полностью

Что и когда меняли в этой оферте?

Первая зафиксированная редакция.

In this article GitHub Bug Bounty Program Legal Safe Harbor Copy markdown In this article Summary We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with...

  • GitHub Bug Bounty Program Legal Safe Harbor
  • In this article
  • Summary
  • 1. Safe Harbor Terms
  • 2. Third Party Safe Harbor
  • 3. Limited Waiver of Other Site Policies