🔒 gliff.ai takes the security of our products very seriously including all our code repositories and dependencies! 🔒
The purpose of this guide is to ensure all contributors and projects within the gliff.ai space have a unified Security Policy to create a fast and informed security vulnerability response whenever one might appear.
Looking for something specific? 🔍
We can currently only support the latest release.
If you believe you have found a security vulnerability in any gliff.ai repository please report it to the team via an email report by contacting us at [email protected].
Please include as much detail in your email report as possible by including a description of the vulnerability covering type of issue, the affected repository, location of affected source code, full paths of source file(s), steps to reproduce including any special configuration, proof-of-concept or exploit code (if possible) and the potential impact. This will help the gliff.ai team better understand the nature and scope of the possible issue and correct the vulnerability ASAP!
A security vulnerability will be responded to as soon as the gliff.ai team are able to. If for some reason a response has not been given within 3 days, please follow up to ensure the team have received the original report.
The gliff.ai team will then aim to release a fix/patch as soon as possible depending on the level of complexity and troubleshooting required.
Have a question? 🧠 Want to report something? 🚨
Reach out to the gliff.ai team at [email protected] or on GitHub.