-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
56 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
# 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 | ||
# Vulnerability Reporting | ||
|
||
## Introduction | ||
|
||
Welcome to the vulnerability reporting process for the VivaMind Assistant project. We take the security of our users seriously, and we appreciate your efforts to disclose any potential vulnerabilities responsibly. | ||
|
||
## Reporting a Vulnerability | ||
|
||
If you believe you have discovered a security vulnerability in the VivaMind Assistant project, please follow these steps to report it: | ||
|
||
1. **Privately Notify Us:** | ||
- Send an email to [yashkulkarni2008@gmail.com](mailto:yashkulkarni2008@gmail.com) with details about the vulnerability. | ||
- Please avoid disclosing the details publicly until we have had a chance to assess and address the issue. | ||
|
||
2. **Include Information:** | ||
- Provide a detailed description of the vulnerability, including steps to reproduce, potential impact, and any proof-of-concept code if applicable. | ||
- Include your contact information for further communication. | ||
|
||
## What to Expect | ||
|
||
Once we receive your vulnerability report, we will acknowledge it promptly and work to validate and address the issue. We may reach out to you for additional details or clarification during the assessment process. | ||
|
||
We are committed to providing regular updates on the progress of resolving the reported vulnerability and will notify you when the issue is fixed. | ||
|
||
## Responsible Disclosure Guidelines | ||
|
||
To promote responsible disclosure, please adhere to the following guidelines: | ||
|
||
- Do not exploit the vulnerability for any reason. | ||
- Do not disclose the vulnerability publicly until it has been resolved. | ||
- Do not share sensitive information with others. | ||
|
||
We appreciate your cooperation in maintaining the security of the VivaMind Assistant project. | ||
|
||
## Hall of Fame | ||
|
||
We would like to express our gratitude to security researchers who responsibly disclose vulnerabilities. A list of contributors to the security of the project will be maintained in our Hall of Fame. | ||
|
||
Thank you for helping us make the VivaMind Assistant project more secure! | ||
|
||
|