We release patches for security vulnerabilities. The following versions are currently being supported with security updates:

We take the security of our project 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: security@temp3.project (Replace with actual 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 following information in your report:

• • Type of vulnerability
  • • Full paths of source file(s) related to the manifestation of 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.

              • Security Update Process

              • When we receive a security bug report, we will:

              • 1. Confirm the problem and determine the affected versions
                2. 2. Audit code to find any potential similar problems
                   3. 3. Prepare fixes for all releases still under maintenance

                      4. 4. Release new security fix versions as soon as possible

                         5. Preferred Languages

                         6. We prefer all communications to be in English or Chinese.

                         7. Disclosure Policy

                         8. We follow a coordinated disclosure policy. Once a security vulnerability has been reported:

                         9. 1. The vulnerability will be confirmed and analyzed
                            2. 2. A fix will be prepared in a private repository
                               3. 3. The fix will be released and announced publicly after a reasonable period

                                  4. 4. Credit will be given to the reporter if desired

                                     5. Security Best Practices

                                     6. When using this project, we recommend:

                                     7. • Always use the latest stable version
                                        • • Regularly update dependencies

                                          • Follow security best practices in your deployment

                                          • Monitor security advisories

                                          • Comments on this Policy

                                          • If you have suggestions on how this process could be improved, please submit a pull request or open an issue to discuss.

                                          ---

                                          Last Updated: 2026-01-04