From 324a576e7a56d551bcdb0711e81580e7a4b65fc2 Mon Sep 17 00:00:00 2001
From: ActYFudgIt <112178161+ActYFudgIt@users.noreply.github.com>
Date: Fri, 26 Aug 2022 06:27:04 -0700
Subject: [PATCH] https://github.com/GitHub

https://bounty.github.com/index.html#scope
Basic writing and formatting syntax
In this article
Headings
Styling text
Quoting text
Quoting code
Supported color models
Links
Section links
Relative links
Images
Lists
Task lists
Mentioning people and teams
Referencing issues and pull requests
Referencing external resources
Uploading assets
Using emoji
Paragraphs
Footnotes
Hiding content with comments
Ignoring Markdown formatting
Disabling Markdown rendering
Further reading
Create sophisticated formatting for your prose and code on GitHub with simple syntax.assurancewireless.comhttps://github.com/contact/report-content?content_url=https%3A%2F%2Fgithub.com%2FSound-Linux-More&report=Sound-Linux-More%20(user)[
---
 SECURITY.md | 30 ------------------------------
 1 file changed, 30 deletions(-)

diff --git a/SECURITY.md b/SECURITY.md
index d9a8762..8b13789 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -1,31 +1 @@
-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)