From a3752176cc03f031afbdc1c2b04c7e219d54c658 Mon Sep 17 00:00:00 2001 From: premier848 Date: Sun, 4 Jan 2026 16:10:35 +0330 Subject: [PATCH] chore: add SECURITY.md for reporting vulnerabilities I have added a SECURITY.md file that outlines the process for users to report any potential security vulnerabilities privately. This aligns with GitHub practices and provides a clear policy for addressing security issues, even in smaller projects. --- SECURITY.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..bacb61a --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,23 @@ +# Security Policy + +## Supported Versions + +Use this section to tell people about which versions of your project are +Currently being supported with security updates. + +| Version | Supported | +| ------- | ------------------ | +| 5.1.x | :white_check_mark: | +| 5.0.x | :x: | +| 4.0.x | :white_check_mark: | +| < 4.0 | :x: | + +## Reporting a Vulnerability + +Use this section to tell people how to report a vulnerability. + +Tell them where to go, how often they can expect to get an update on a +reported vulnerability, what to expect if the vulnerability is accepted or +declined, etc. + +If you discover a security vulnerability in this project, please report it via GitHub's private vulnerability reporting feature.