The Assembly 300 Snippets repository is a collection of educational code snippets and does not have versioned releases. All snippets in the main branch are considered the latest and supported for security updates.

We take security seriously and appreciate your efforts to responsibly disclose any vulnerabilities found in the Assembly 300 Snippets repository.

1. Email: Send a detailed description of the vulnerability to izeno.contact@gmail.com. Include:
   • A clear description of the issue, including affected snippets or files.
   • Steps to reproduce the vulnerability.
   • Potential impact (e.g., code execution, data exposure).
   • Any suggested fixes (optional).
2. GitHub Issue: Alternatively, open a private issue in the GitHub Issues section, using the "Security Vulnerability" issue template.

• Acknowledgment: You will receive an acknowledgment of your report within 48 hours.
• Investigation: The maintainer (@VoxDroid) will investigate and assess the vulnerability within 7 days.
• Resolution: If valid, the vulnerability will be fixed, and the fix will be documented in the relevant snippet’s README.md or the main README.md. You may be credited (with your permission) in the fix notes.
• Declined Reports: If the report is not a valid vulnerability, you will be notified with an explanation.

• Responsible Disclosure: Do not publicly disclose the vulnerability until it has been resolved.
• Scope: Vulnerabilities should pertain to the assembly code or documentation in this repository. General Linux or NASM vulnerabilities should be reported to their respective maintainers.
• No Exploitation: Do not exploit vulnerabilities beyond what is necessary to demonstrate the issue.

For security-related questions, email izeno.contact@gmail.com.

Thank you for helping keep Assembly 300 Snippets secure!