No conflicting license combinations in production dependencies

License incompatibilities create legal obligations that may be impossible to satisfy simultaneously. GPL-2.0 and Apache-2.0 are considered mutually incompatible for combined works because the Apache patent termination clause is inconsistent with GPL-2.0's terms — the FSF and OSI both document this. If your production application statically links both, the resulting combined work cannot be legally distributed under either license. Creative Commons licenses applied to code — rather than content — create a different set of incompatibilities with standard software licenses. The consequence is that your software may not legally be shipped or distributed in its current form, regardless of your intent or how the components are actually used at runtime.

Enumerate all unique license types across production dependencies and check for known conflicts:

npx license-checker --production --summary
# Or fail the build on specific combinations:
npx license-checker --production --failOn 'GPL-2.0;GPL-3.0;AGPL-3.0'

For detected conflicts, replace one of the conflicting packages with a permissively-licensed alternative. If the conflict involves a niche package with no alternative, consult a software licensing attorney — the SaaS vs. distribution distinction matters significantly under GPL-2.0 and Apache-2.0.