Skip to content
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.

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

docs: Add security policy file #170

Open
wants to merge 3 commits into
base: kotlin
Choose a base branch
from

Conversation

validcube
Copy link
Member

SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
Copy link
Member

@oSumAtrIX oSumAtrIX left a comment

Choose a reason for hiding this comment

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

Some references to ReVanced Manager have to be changed to ReVanced API

@oSumAtrIX oSumAtrIX marked this pull request as draft February 9, 2024 11:43
SECURITY.md Show resolved Hide resolved
@oSumAtrIX oSumAtrIX changed the title Security policy for api kotlin docs: Add security policy file Feb 9, 2024
Co-authored-by: oSumAtrIX <johan.melkonyan1@web.de>
SECURITY.md Outdated Show resolved Hide resolved
@validcube validcube marked this pull request as ready for review February 15, 2024 02:36
@alexandreteles
Copy link
Member

Technically the only supported version is whatever is in production (main) and Dev works as staging grounds for changes before moving those into production. Might want to change that before merging.

@validcube
Copy link
Member Author

Technically the only supported version is whatever is in production (main) and Dev works as staging grounds for changes before moving those into production. Might want to change that before merging.

I think development branch should be included, because it allows people to flag a security vulnerability during development which helps us fix a security hole before merging to production.

@alexandreteles
Copy link
Member

Technically the only supported version is whatever is in production (main) and Dev works as staging grounds for changes before moving those into production. Might want to change that before merging.

I think development branch should be included, because it allows people to flag a security vulnerability during development which helps us fix a security hole before merging to production.

We can integrate it, but I'm not providing security updates to development versions :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants