Skip to content

chore: add securitiy policy #595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JoanFM merged 2 commits into from
Oct 7, 2022
Merged

chore: add securitiy policy #595

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d1b32c
chore: add securitiy policy
samsja Oct 7, 2022
3060ff6
feat: apply nicholas suggestion
samsja Oct 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Security Policy

Security is very important for DocArray and its community.

## Supported Versions

The latest versions of DocArray are supported.
Copy link
Copy Markdown
Contributor

@NicholasDunham NicholasDunham Oct 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this specific enough? Do we mean the latest version, the latest two versions, or the latest five versions? Minor versions or patch versions?

Copy link
Copy Markdown
Member Author

@samsja samsja Oct 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I copy past from jina core tbh.

I think that it means that the last minor version is supported as our plan now is not maintain older minor version (ex 3.0) since we merge bug fix in the newer version



## Reporting a Vulnerability

If you think you've found a vulnerability, even if you are not sure about it, please report it right away by sending an email to [email protected]. Please try to be as explicit as possible, describing all the steps and example code to reproduce the security issue.

Our team will review it thoroughly and get back to you.

Please refrain from publicly discussing a potential security vulnerability on Github issues or in Slack community. It's better to discuss it privately and try to find a solution first, to limit the potential impact as much as possible.