Use this section to tell people about which versions of your project are currently being supported with security updates.

We take security vulnerabilities seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to [INSERT SECURITY EMAIL].

You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

• Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the vulnerability
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit it

This information will help us triage your report more quickly.

We prefer all communications to be in English.

NexusDI follows the principle of Responsible Disclosure.

We would like to thank all security researchers and users who report security vulnerabilities to us. Your efforts help us maintain the security and privacy of our users.

When using NexusDI, please follow these security best practices:

1. Keep dependencies updated: Regularly update NexusDI and its dependencies
2. Validate inputs: Always validate and sanitize user inputs
3. Use HTTPS: Use HTTPS in production environments
4. Follow principle of least privilege: Only grant necessary permissions
5. Regular security audits: Conduct regular security reviews of your code

Security updates will be released as patch versions (e.g., 0.1.1, 0.1.2) and will be clearly marked in the changelog.