Differences (features or ideal use cases) comparing with SecKit

The two modules are not incompatible, provided the CSP settings in Seckit are disabled (and CSP module will add a warning to the site status page if so), since Seckit offers other features than setting a CSP header.

Seckit offers a single, static, policy for a site defined in strings.

- CSP's configuration is structured and granular, with concurrent reported and enforced policies.
- CSP provides an API for dynamic alterations, which it uses to automatically add necessary sources according to a site's library definitions.
- other modules already integrate with CSP's API, to ensure a site's policy allows their functionality without a site builder needing to make any config changes.
- helper methods and services are available to ensure devs safely alter policies
- integrations are available for Reporting API module, Report-URI.com, Sentry...

See also 🌱 Deprecate / Remove Content Security Policy configuration in favour of Content Security Policy module Active

Automatically closed - issue fixed for 2 weeks with no activity.