Create SECURITY.md

Signed-off-by: Gideon Selorm Ayivi <88237474+SelormDev@users.noreply.github.com>

Author: SelormDev

SECURITY.md

@@ -0,0 +1,52 @@
+# Security Policy
+
+---
+
+## Supported Versions
+
+| Version  | Supported          |
+|----------|--------------------|
+| Main     | :white_check_mark: |
+| Others   | :x:                |
+
+Only the `main` branch is actively monitored for security issues. Ensure you are using the latest version of the repository.
+
+---
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please report it responsibly by following these steps:
+
+1. **Contact Me Directly**  
+   Send me an [email](mailto:info@selormdev.com) with the subject line: `Security Vulnerability Report`.  
+   Include:
+   - A detailed description of the vulnerability.
+   - Steps to reproduce the issue.
+   - Any additional information that might be helpful.
+
+2. **Do Not Disclose Publicly**  
+   Please avoid public discussions about the vulnerability until it has been addressed.
+
+3. **Acknowledgment**  
+   I will acknowledge your report within 48 hours and work towards resolving the issue promptly.
+
+---
+
+## Vulnerability Management
+
+Once a security issue is reported:
+1. The issue will be reviewed and verified.
+2. A fix will be implemented and tested.
+3. A patch will be released and communicated in the repository.
+
+---
+
+## General Security Practices
+
+While this repository is primarily for coursework and personal use:
+- Ensure you only use trusted external resources or dependencies.
+- Avoid exposing sensitive information like API keys or personal data.
+
+---
+
+Thank you for helping to keep this repository secure! This document outlines the security practices and how to report vulnerabilities.