March 2025
Intermediate to advanced
470 pages
12h 45m
English
Yes, obligations vary across the FOSS licensing landscape. That doesn’t mean license compliance needs to be a convoluted mess. In fact, three basic steps will cover the majority of your license compliance needs (and one of them is optional for a subset of licenses): checking for compatibility, giving attribution, and providing source code.
FOSS licenses generally mingle pleasantly together in a software codebase, but a few don’t get on well at all. For instance, Apache-2.0 and GPL-2.0 don’t play nicely together,[93] which can be problematic since these two FOSS licenses are popular. When reviewing the licenses represented in your SSC, make sure they’re compatible with each other. The license compatibility ...
Read now
Unlock full access