If you discover a security vulnerability in this project, please report it to us by emailing mail [at] anheledir.net. Please do not disclose the vulnerability publicly until we have had a chance to address it.

When reporting a vulnerability, please include the following information:

• A description of the vulnerability, including how it can be reproduced
• Steps we can follow to reproduce the vulnerability
• Any additional information that could help us understand and fix the issue

We will investigate all reports of security vulnerabilities and do our best to address them as quickly as possible.

This product is currently in pre-release version 0.x and is actively being developed. We support the latest pre-release version and may provide security updates as needed.

Please note that pre-release versions of the product are not intended for production use and may contain bugs, security vulnerabilities, or other issues. We encourage you to test the pre-release version in a development or testing environment only.

We do not provide support for older pre-release versions of the product. If you are using an older version of the pre-release product, we recommend upgrading to the latest pre-release version to ensure that you have the latest features and bug fixes.

Once the product reaches a stable release, we will provide support for the current version and the previous major release with security updates. Until then, we recommend keeping up-to-date with the latest pre-release version to ensure that you have the latest features and bug fixes.

We will release security updates for this project as needed. These updates will be included in the next release of the project, as well as in any patch releases for supported versions.

We encourage all users of this project to update to the latest version as soon as possible to ensure that you have the latest security updates.

To help ensure the security of this project, we recommend the following best practices:

• Keep your dependencies up-to-date with the latest security patches
• Use strong, unique passwords for all accounts associated with this project
• Use two-factor authentication wherever possible
• Follow secure coding practices, including input validation and output encoding
• Test your code thoroughly, including for common security vulnerabilities like cross-site scripting (XSS) and SQL injection
• Use a content security policy (CSP) to protect against common web vulnerabilities
• Use TLS/SSL to encrypt all data in transit
• Limit the use of sensitive data to only those who need it
• Regularly review access logs and monitor for suspicious activity

By following these best practices, you can help ensure that your use of this project is as secure as possible.