Thank you for helping keep AlphaLab secure.

Security is an important part of building reliable quantitative research and trading infrastructure. If you discover a security issue, we appreciate responsible disclosure.

Only the latest stable release receives security updates.

Please do not open a public GitHub Issue for security vulnerabilities.

Instead, privately contact the project maintainers with the following information:

• Description of the vulnerability
• Steps to reproduce
• Potential impact
• Suggested mitigation (if known)
• Proof of concept (if appropriate)

Reports should provide enough information for maintainers to reproduce and investigate the issue.

We ask that you:

• Allow maintainers reasonable time to investigate.
• Avoid publicly disclosing vulnerabilities before a fix is available.
• Act in good faith to protect project users.

We are committed to investigating all legitimate reports.

Examples of security-related issues include:

• Remote code execution
• Privilege escalation
• Authentication bypass
• Sensitive data exposure
• Dependency vulnerabilities
• Unsafe default behavior
• Arbitrary file access

General bugs, feature requests, and documentation issues should be reported through the normal GitHub issue tracker.

AlphaLab depends on third-party Python packages.

While we strive to keep dependencies up to date, security issues originating from external libraries should also be reported to the corresponding upstream maintainers where appropriate.

Users are encouraged to:

• Keep AlphaLab updated to the latest stable release.
• Use supported versions of Python.
• Regularly update project dependencies.
• Review configuration before deploying to production.
• Avoid storing credentials directly in source code.

We appreciate everyone who responsibly reports security issues and helps improve the reliability and safety of AlphaLab.