Create an issue using 'Report a security vulnerability' template. We will try to fix it as soon as possible.

We will try to fix the vulnerability as soon as possible. We will release a new version with the fix and publish it to the marketplace. We will also update the changelog and release notes with the details of the vulnerability and the fix.

Following the semantic versioning as per semver.org, we will release a new patch version for each major.minor version. For example, if the current version is 1.2.3, we will release a new version 1.2.4 with the fix. If the current version is 1.2.0, we will release a new version 1.2.1 with the fix.

If the vulnerability is critical, we will release a new minor version. For example, if the current version is 1.2.3, we will release a new version 1.3.0 with the fix. If the current version is 1.2.0, we will release a new version 1.3.0 with the fix.

If the vulnerability is critical and the fix is not backward compatible, we will release a new major version. For example, if the current version is 1.2.3, we will release a new version 2.0.0 with the fix. If the current version is 1.2.0, we will release a new version 2.0.0 with the fix.

We will try to fix the vulnerability as soon as possible. We will release a new version with the fix and publish it to the marketplace. We will also update the changelog and release notes with the details of the vulnerability and the fix.

If you believe someone is violating the Code of Conduct, we ask that you report it by emailing the team at team@codevedas.com