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

We take the security of FreeDevTools 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 [email protected]/freedevtools/t/.

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.

After you submit a security report, you can expect:

1. Initial Response: We'll acknowledge receipt of your report within 48 hours
2. Assessment: Our security team will investigate and assess the reported vulnerability
3. Updates: We'll keep you informed of our progress and any questions we may have
4. Resolution: Once the issue is resolved, we'll notify you and credit you in our security advisory (if you wish)

When we receive a security bug report, we will:

1. Confirm the problem and determine the affected versions
2. Audit code to find any similar problems
3. Prepare fixes for all supported versions
4. Release a new version with the fix
5. Credit the reporter in our security advisory

To help keep FreeDevTools secure, we recommend:

• Keep your dependencies updated
• Use HTTPS for all communications
• Validate and sanitize all user inputs
• Follow the principle of least privilege
• Regularly audit your code for security issues
• Use security scanning tools in your CI/CD pipeline

Security advisories will be published on our GitHub Security Advisories page and announced through our release notes.

We would like to thank all security researchers who responsibly disclose vulnerabilities to us. Your contributions help make FreeDevTools more secure for everyone.

For security-related questions or concerns, please contact us at [email protected].

Thank you for helping keep FreeDevTools and our users secure! 🛡️