swagger2krakend does not publish tagged releases yet. Security fixes are applied to the main branch.

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, use one of these channels:

1. GitHub private vulnerability reporting (preferred): go to the Security tab of this repository and click "Report a vulnerability".
2. Email: contact@optimce.be.

Please include as much of the following as you can:

• The type of issue (e.g. injection, path traversal, information disclosure)
• The affected file(s), configuration input, or component
• Step-by-step instructions to reproduce the issue, or a proof of concept
• The impact you believe the issue has, and how an attacker might exploit it

OptimCE is maintained by a small team. We aim to acknowledge your report within a few business days, keep you informed while we investigate, and credit you in the fix (unless you prefer to remain anonymous). Please give us a reasonable amount of time to address the issue before any public disclosure.

This repository contains the swagger2krakend configuration generator, one of the tooling repositories of the OptimCE platform. Vulnerabilities in this tool — for example in Jinja2 variable substitution, file handling, or the generated KrakenD configuration — belong here. If the issue affects a different OptimCE service, you can report it in that service's repository; if you are unsure, reporting it here (or by email) is fine — we will route it to the right place.