This project may handle sensitive configurations, credentials, or system interactions. Security is a top priority, and we take all vulnerability reports seriously.

If you discover a security issue, please report it responsibly.

Do not open a public GitHub issue for security vulnerabilities.

Instead, report the issue through one of the following:

• GitHub Security Advisories (if enabled), or
• Contact the repository maintainers privately, or
• Report via our dedicated support email for vulnerabilities

Provide as much detail as possible:

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

⚠️ Important: Remove any sensitive information (credentials, tokens, private URLs, etc.) before sharing logs or examples.

Once a vulnerability is reported:

1. Maintainers will review and validate the issue
2. A Jira ticket will be created internally to track the fix
3. The issue will be addressed through our internal development process
4. A fix will be included in a future release

Maintainers may reach out for clarification or additional details during this process.

Examples include (but are not limited to):

• Credential exposure or leakage
• Unsafe default behavior leading to unintended destructive actions
• Improper permission or access control handling
• Injection vulnerabilities (e.g., command, query, or script injection)
• Privilege escalation scenarios
• Insecure handling of configuration or environment data

If you're unsure whether something qualifies, report it privately and we will evaluate it.

We request that you:

• Do not publicly disclose the issue until it has been addressed
• Give maintainers reasonable time to investigate and fix the problem

We appreciate your help in keeping this project and its users secure.

Security fixes are typically delivered as part of regular releases. In some cases, critical fixes may be prioritized and released sooner.