forked from n4ze3m/dialoqbase
-
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
35 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,35 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
Currently, we are supporting security updates for the following versions of `dialoqbase`: | ||
|
||
| Version | Supported | | ||
| ------- | ------------------| | ||
| 1.x | ✅ | | ||
| < 1.0 | ❌ | | ||
|
||
## Reporting a Vulnerability | ||
|
||
Your assistance in identifying and reporting security vulnerabilities is invaluable. We prioritize the safety and security of our application. If you believe you've identified a security vulnerability in `dialoqbase`, please reach out to us as described below. | ||
|
||
### Guidelines | ||
|
||
- Kindly grant us a reasonable time frame to address vulnerabilities before any public disclosure. | ||
- Please avoid using the public issue tracker for reporting security issues. Instead, refer to the contact information below. | ||
- The more detailed your report, the quicker we can reproduce and address any potential vulnerabilities. | ||
|
||
### Contact | ||
|
||
For any security vulnerability, please email [email protected]. | ||
|
||
### Response Expectations | ||
|
||
When we receive a report concerning a vulnerability, our general process is as follows: | ||
|
||
1. Acknowledge the receipt of your report within 72 hours. | ||
2. Investigate the issue and provide an initial response within a week, confirming or refuting the vulnerability, and if confirmed, classifying its severity. | ||
3. Proceed with corrective actions and communicate the progress to the reporter. | ||
|
||
We appreciate your collaboration in ensuring `dialoqbase` remains secure for all users! | ||
|