From f8dc47f27fd82d351c033b4a0114504e60bc3240 Mon Sep 17 00:00:00 2001 From: Dipanita45 <132455672+Dipanita45@users.noreply.github.com> Date: Sun, 3 Nov 2024 21:27:43 +0530 Subject: [PATCH 1/3] Create SECURITY.md --- SECURITY.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..205533e --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,25 @@ +Security Policy +Supported Versions +The following versions of Revot are currently supported with security updates: + +Version Supported +1.x.x ✅ Supported +0.x.x ❌ Not supported +Reporting a Vulnerability +If you discover a security vulnerability in Revot, we encourage you to report it as soon as possible. We will investigate all legitimate reports and do our best to quickly fix the issue. + +# How to Report +Please report vulnerabilities by emailing us at revot@gmail.com. Include as much detail as possible to help us identify and fix the issue swiftly. +Do not share the vulnerability publicly until it has been addressed and a patch is available. +Security Updates +We will notify users via GitHub releases for any critical security updates. +Minor security patches will be included in regular updates as needed. + +# Security Best Practices +Make sure to use the latest version of Revot for the latest security features and patches. +Follow password best practices, such as using strong, unique passwords for each account. +Regularly update your dependencies to the latest versions. + +# Acknowledgements +We appreciate contributions from the community and researchers who help us improve the security of Revot. Thank you for keeping the platform secure for everyone! + From e0e38ab744ab212729507c06cd6b4a20356dd6a7 Mon Sep 17 00:00:00 2001 From: Dipanita45 <132455672+Dipanita45@users.noreply.github.com> Date: Sun, 3 Nov 2024 21:51:58 +0530 Subject: [PATCH 2/3] Update SECURITY.md --- SECURITY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 205533e..02953bb 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -3,13 +3,13 @@ Supported Versions The following versions of Revot are currently supported with security updates: Version Supported -1.x.x ✅ Supported +1.0.0 ✅ Supported 0.x.x ❌ Not supported Reporting a Vulnerability If you discover a security vulnerability in Revot, we encourage you to report it as soon as possible. We will investigate all legitimate reports and do our best to quickly fix the issue. # How to Report -Please report vulnerabilities by emailing us at revot@gmail.com. Include as much detail as possible to help us identify and fix the issue swiftly. +Please report vulnerabilities by emailing us at prashantandoriya@gmail.com. Include as much detail as possible to help us identify and fix the issue swiftly. Do not share the vulnerability publicly until it has been addressed and a patch is available. Security Updates We will notify users via GitHub releases for any critical security updates. From 4517927b7a793883deb7a7350236570559a30137 Mon Sep 17 00:00:00 2001 From: Dipanita45 <132455672+Dipanita45@users.noreply.github.com> Date: Sun, 3 Nov 2024 21:53:28 +0530 Subject: [PATCH 3/3] Update SECURITY.md --- SECURITY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 02953bb..1f61608 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -3,13 +3,13 @@ Supported Versions The following versions of Revot are currently supported with security updates: Version Supported -1.0.0 ✅ Supported +3.12.0 ✅ Supported 0.x.x ❌ Not supported Reporting a Vulnerability If you discover a security vulnerability in Revot, we encourage you to report it as soon as possible. We will investigate all legitimate reports and do our best to quickly fix the issue. # How to Report -Please report vulnerabilities by emailing us at prashantandoriya@gmail.com. Include as much detail as possible to help us identify and fix the issue swiftly. +Please report vulnerabilities by emailing us at minhajulhossain@gmail.com Include as much detail as possible to help us identify and fix the issue swiftly. Do not share the vulnerability publicly until it has been addressed and a patch is available. Security Updates We will notify users via GitHub releases for any critical security updates.