Describe here all the security policies in place on this repository to help your contributors to handle security issues efficiently.

⚠️You must never store credentials information into source code or config file in a GitHub repository

• Block sensitive data being pushed to GitHub by git-secrets or its likes as a git pre-commit hook
• Audit for slipped secrets with dedicated tools
• Use environment variables for secrets in CI/CD (e.g. GitHub Secrets) and secret managers in production

This is the currently supported versions:

Please report a vulnerability through the issue tracker by specifying the 'security' label.

You can ask for support by contacting [email protected]

In the case a vulnerability is found, you can always contact one of the administrators of this provide to provide more information or create a an issue ticket with the 'security' label. It is important that if you decide to create an issue in the issue tracker that the description of the vulnerability should be high-level and not contain exact exploitation steps.

TBD

TBD

• Currently the internal browser is used to access internal links (#137)