The following are the compatible versions (target frameworks) of the project that are supported with security updates:

• .NET:

  • net5.0, net5.0-windows
  • net6.0, net6.0-android, net6.0-ios, net6.0-maccatalyst, net6.0-macos, net6.0-tvos, net6.0-windows
  • net7.0, net7.0-android, net7.0-ios, net7.0-maccatalyst, net7.0-macos, net7.0-tvos, net7.0-windows
  • net8.0, net8.0-android, net8.0-browser, net8.0-ios, net8.0-maccatalyst, net8.0-macos, net8.0-tvos, net8.0-windows

• .NET Core:

  • netcoreapp2.0, netcoreapp2.1, netcoreapp2.2
  • netcoreapp3.0, netcoreapp3.1

• .NET Standard:

  • netstandard2.0, netstandard2.1

• .NET Framework:

  • net461, net462, net463, net47, net471, net472, net48, net481

• MonoAndroid:

  • monoandroid

• MonoMac:

  • monomac

• MonoTouch:

  • monotouch

• Tizen:

  • tizen40, tizen60

• Xamarin.iOS:

  • xamarinios

• Xamarin.Mac:

  • xamarinmac

• Xamarin.TVOS:

  • xamarintvos

• Xamarin.WatchOS:

  • xamarinwatchos

If you discover a security vulnerability in this project, please follow these steps to report it:

1. Contact Us: Send an email to pabloperdomofalcon@gmail.com. Please include detailed information about the vulnerability, including steps to reproduce and any potential impact.

2. Response Time: We aim to respond to all security reports within 72 hours. We will acknowledge receipt of your report and provide you with an estimated timeline for resolution.

3. Evaluation: Our team will review the report and assess the severity of the vulnerability. We will then determine whether the vulnerability is valid and how it will be addressed. You will receive an update on the status of your report, whether it is accepted or declined.

4. Disclosure: Once a fix has been implemented and released, we will provide a detailed description of the vulnerability and the resolution in our release notes and security updates. We will also notify you directly.

5. Responsible Disclosure: Please do not disclose the vulnerability publicly until a fix has been released. This helps us to address the issue effectively and protect users.

• Release Schedule: Security updates are released as part of our regular release cycle. Critical fixes may be released as hotfixes outside of the regular schedule if necessary.
• Changelog: Detailed information about each security update, including the nature of the fix and affected components, will be documented in our changelog.

• Code Review: All code changes, especially those affecting security, are reviewed by multiple team members to ensure adherence to security best practices.
• Testing: We use automated and manual testing to identify vulnerabilities. Security-related tests are included in our continuous integration pipeline.
• Dependencies: We regularly update and audit our dependencies to address known vulnerabilities in third-party libraries.

• Disclosure: Information about known vulnerabilities, including details on affected versions and mitigation steps, will be shared in our public issue tracker or release notes.
• Updates: We will provide updates on the status of known vulnerabilities and the steps we are taking to address them.

For any questions or additional information regarding our security policy, please contact us at pabloperdomofalcon@gmail.com.