Удалено
- Удалено: github
- Удалено: /
- Удалено: site-policy
- Удалено: Public
- Удалено: Notifications
- Удалено: You must be signed in to change notification settings
- Удалено: Fork
- Удалено: Star
- Удалено: 2.2k
Недавно обновлялась — последняя правка 3 дня назад. Обычно меняется часто — примерно раз в 1 день.
Поделиться
Это оглавление: ниже отдельные оферты и политики, которые входят в раздел.
У компании в каталоге есть и другие оферты — их история ведётся так же.
Каждая строка — одна зафиксированная правка. Пункт считается изменённым, если его текст стал другим; добавленные и удалённые считаются отдельно.
| Дата правки | Пунктов изменено | Новых пунктов | Убрано пунктов |
|---|---|---|---|
| 0 | 0 | 0 | |
| 0 | 0 | 0 | |
| 0 | 0 | 0 | |
| 0 | 0 | 0 | |
| 0 | 0 | 0 | |
| 0 | 0 | 0 |
Редакция от .
Security: github/site-policy Security Report a vulnerability SECURITY.md Thanks for helping make GitHub safe for everyone. Security GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our Gi...
Report a vulnerability
SECURITY.md
Thanks for helping make GitHub safe for everyone.
GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as GitHub.
Even though open source repositories are outside of the scope of our bug bounty program and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Instead, please send an email to opensource-security[@]github.com.
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
Full paths of source file(s) related to the manifestation of the issue
The location of the affected source code (tag/branch/commit or direct URL)
Any special configuration required to reproduce the issue
Step-by-step instructions to reproduce the issue
Proof-of-concept or exploit code (if possible)
Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
See GitHub's Safe Harbor Policy
Это начало документа. Читать полностью
Удалено