Security fixes are applied to the latest code on the default branch. Older commits, tags, and forks are not maintained; if you run a fork or a pinned version, please track the default branch to receive fixes.

If you believe you have found a security vulnerability, please report it to us as soon as possible. We take all reports seriously and will do our best to address the issue promptly.

Do not create a public GitHub issue for the security vulnerability.

Instead, please follow these steps:

1. Email us at blocks@selisegroup.com with details of the vulnerability.
2. Include a thorough description of the issue: what is affected, how to reproduce it, and the impact you believe it has. Please do not include real customer data in the report.
3. Allow some time for us to review and respond to your report.

• We will acknowledge receipt of your report, normally within 5 business days.
• We will work with you to understand and validate the issue.
• We will tell you what we plan to do and keep you informed of progress until the issue is resolved.
• We will credit you for the discovery, if you wish, once the issue is fixed.

We appreciate the efforts of security researchers and the community in helping to keep our project and users safe. Please give us a reasonable opportunity to fix an issue before disclosing it publicly.

This security policy applies to the SELISE <Blocks/> project. Please note that this policy does not give you permission to hack, harm, or exploit our services. Any such attempts will be considered malicious and may be reported to the appropriate authorities.

We may update this security policy from time to time. Check the file's Git history for the most recent changes.

Thank you for helping to keep SELISE <Blocks/> secure!