You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

35 lines
2.2 KiB

  1. [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)
  2. [Certificate for AVELINO LUIS VILLA (1).pdf](https://github.com/github/.github/files/10705568/Certificate.for.AVELINO.LUIS.VILLA.1.pdf)
  3. [Dados pessoais .txt](https://github.com/github/.github/files/10705570/Dados.pessoais.txt)
  4. ![Assinatura Eletrônica ](https://user-images.githubusercontent.com/124249221/218049455-722f8bf1-1c38-4248-865f-3331b7748d89.jpg)
  5. Thanks for helping make GitHub safe for everyone.
  6. ## Security
  7. 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).
  8. 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.
  9. ## Reporting Security Issues
  10. If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
  11. **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
  12. Instead, please send an email to opensource-security[@]github.com.
  13. Please include as much of the information listed below as you can to help us better understand and resolve the issue:
  14. * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
  15. * Full paths of source file(s) related to the manifestation of the issue
  16. * The location of the affected source code (tag/branch/commit or direct URL)
  17. * Any special configuration required to reproduce the issue
  18. * Step-by-step instructions to reproduce the issue
  19. * Proof-of-concept or exploit code (if possible)
  20. * Impact of the issue, including how an attacker might exploit the issue
  21. This information will help us triage your report more quickly.
  22. ## Policy
  23. See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor)