deepdata: product docs, rebranded quick start, security policy
This commit is contained in:
+32
@@ -0,0 +1,32 @@
|
||||
# Security Policy
|
||||
|
||||
## Supported Versions
|
||||
|
||||
Only the latest release of deepdata is supported with security updates.
|
||||
|
||||
| Version | Supported |
|
||||
| ------- | ------------------ |
|
||||
| latest | :white_check_mark: |
|
||||
| older | :x: |
|
||||
|
||||
## Reporting a Vulnerability
|
||||
|
||||
Please **do not** report security vulnerabilities through public GitHub-style
|
||||
issue trackers or pull requests.
|
||||
|
||||
Report suspected security vulnerabilities privately by opening a Gitea issue
|
||||
with the `security` label on this repository:
|
||||
|
||||
```
|
||||
https://gitea.apescale.com/figmar/deepdata/issues
|
||||
```
|
||||
|
||||
Include in your report:
|
||||
|
||||
- A description of the vulnerability and its impact
|
||||
- The affected component and version
|
||||
- Steps or a proof of concept to reproduce the issue (where possible)
|
||||
|
||||
We aim to acknowledge all reports within 3 business days and will keep you
|
||||
updated on the status of your report. Please do not disclose a vulnerability
|
||||
publicly until we have confirmed a fix or completed an assessment.
|
||||
Reference in New Issue
Block a user