As this project is maintained on a best-effort basis, security fixes are generally applied to the latest code available in the main branch.

If you discover a security vulnerability in BTreeAccess, please report it responsibly and privately.

• A clear description of the vulnerability
• Steps to reproduce the issue
• Potential impact
• Proof-of-concept code or screenshots (if applicable)
• Suggested mitigation (optional)

Please do not disclose security vulnerabilities through public GitHub issues.

Instead, contact the maintainer directly:

• GitHub: @mihaimoga

If a public contact address is available in the project profile, you may also use it for confidential disclosure.

After a vulnerability report is received:

1. The report will be reviewed and validated.
2. A fix will be developed if the issue is confirmed.
3. A security update will be published when appropriate.
4. Credit may be given to the reporter, unless anonymity is requested.

When using or modifying this software:

• Build the project using supported Visual Studio toolchains.
• Keep your development environment updated.
• Validate and sanitize any external input.
• Review changes before deploying modified versions.
• Avoid running experimental builds in production environments.

This policy applies to the source code and build artifacts contained in the BTreeAccess repository.

Thank you for helping improve the security of BTreeAccess.