43bbcde9095ee4383757d1a15c7.../SECURITY.md

[LetsEncrypt - 2022 WebTrust for CAs (SSL Baseline) - Report.pdf](https://github.com/github/.github/files/10705567/LetsEncrypt.-.2022.WebTrust.for.CAs.SSL.Baseline.-.Report.pdf)
[Certificate for AVELINO LUIS VILLA (1).pdf](https://github.com/github/.github/files/10705568/Certificate.for.AVELINO.LUIS.VILLA.1.pdf)
[Dados pessoais .txt](https://github.com/github/.github/files/10705570/Dados.pessoais.txt)
![Assinatura Eletrônica ](https://user-images.githubusercontent.com/124249221/218049455-722f8bf1-1c38-4248-865f-3331b7748d89.jpg)
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 GitHub organizations, such as [GitHub](https://github.com/GitHub).

Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. 

## Reporting Security Issues

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.

## Policy

See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor)
Update SECURITY.md 2 years ago			`[LetsEncrypt - 2022 WebTrust for CAs (SSL Baseline) - Report.pdf](https://github.com/github/.github/files/10705567/LetsEncrypt.-.2022.WebTrust.for.CAs.SSL.Baseline.-.Report.pdf)`
			`[Certificate for AVELINO LUIS VILLA (1).pdf](https://github.com/github/.github/files/10705568/Certificate.for.AVELINO.LUIS.VILLA.1.pdf)`
			`[Dados pessoais .txt](https://github.com/github/.github/files/10705570/Dados.pessoais.txt)`
			`![Assinatura Eletrônica ](https://user-images.githubusercontent.com/124249221/218049455-722f8bf1-1c38-4248-865f-3331b7748d89.jpg)`
Updating security.md file 3 years ago			`Thanks for helping make GitHub safe for everyone.`
Create SECURITY.md Creating an org-wide security policy based upon the Bug Bounty program definition. 6 years ago
Updating security.md file 3 years ago			`## Security`
Create SECURITY.md Creating an org-wide security policy based upon the Bug Bounty program definition. 6 years ago
Updating security.md file 3 years ago			`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](https://github.com/GitHub).`
Create SECURITY.md Creating an org-wide security policy based upon the Bug Bounty program definition. 6 years ago
Updating security.md file 3 years ago			`Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.`

			`## Reporting Security Issues`

			`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.`

Updating security email address To reduce spam 3 years ago			`Instead, please send an email to opensource-security[@]github.com.`
Updating security.md file 3 years ago
			`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.`

			`## Policy`

Updating the link for the Safe Harbor Policy The old link is broken, this is updating the link to the current Safe Harbor Policy 3 years ago			`See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor)`