chore: Create Security Policy (#213)

Adding our default security policy to this project

SECURITY.md

@@ -0,0 +1,30 @@
+# Security Policy
+
+**Do not report security vulnerabilities through public GitHub issues.**
+
+**Please use the [Private Vulnerability Disclosure](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability) feature of GitHub.**
+
+Alternatively, you can also send them by email to [email protected].
+You can encrypt your mail using GnuPG if you want. 
+
+See the [security.txt](https://crabnebula.dev/.well-known/security.txt) from CrabNebula
+
+```
+Contact: mailto:[email protected]
+Expires: 2025-01-30T06:30:00.000Z
+Encryption: https://crabnebula.dev/.well-known/pgp.txt
+Preferred-Languages: en,de,fr
+Canonical: https://crabnebula.dev/.well-known/security.txt
+```
+
+Include as much of the following information:
+
+- Type of issue (e.g. buffer overflow, privilege escalation, etc.)
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- The distribution affected or used for reproduction.
+- Step-by-step instructions to reproduce the issue
+- Impact of the issue, including how an attacker might exploit the issue
+- Preferred Languages
+
+We prefer to receive reports in English. If necessary, we also understand French and German.