Dear Marteen,
You're correct, the current Content-Security-Policy header includes unsafe-inline for the style-src directive. In the past, we explicitly added a CSP header for other security-related reasons.
As a consequence, it became necessary to also include 'unsafe-inline' for styles, since omitting style-src would cause the browser to fall back to default-src, which would block inline styles.
This would break the UI, as inline styling is currently widely used throughout VocBench.
At the moment, the CSP header is hardcoded and cannot be customized without releasing a new version (or without manually rebuilding the backend).
Moreover, even if the directive were removed, it would break the UI unless all inline style="..." usages were refactored into CSS classes, which is currently not feasible given how extensively inline styles are used throughout the components.
We acknowledge the concern and will take it into account when planning future refactoring. That said, this is not something currently scheduled in the short term.
Best regards,
Tiziano