There is a "security" tab in the airflow repository where code scanning produces new issues discovered in our code.
In order to drag attention to it, we should have an automation to post slack messages in a private "security" channel - this, similarly as in case of main failures - might help us with more "group" handling of noticing and handling such security reports.
There is a "security" tab in the airflow repository where code scanning produces new issues discovered in our code.
In order to drag attention to it, we should have an automation to post slack messages in a private "security" channel - this, similarly as in case of main failures - might help us with more "group" handling of noticing and handling such security reports.