Say I have a web page:

<!-- A custom javascript library -->
<script src="myCustomScript.js"></script>

<!-- A GPL2 javascript library -->
<script src="GPLv2Library.js"></script>

<!-- A MIT licensed javascript library -->
<script src="MITLibrary.js"></script>


//other custom javascript



Does the presence of the GPL2 library affect the licence options for the custom scripts (assuming the GPL2 licence text is included in the GPL2 library source and that the source code has not been modified), or the MIT licensed library?

Does the whole webpage/application escape being classified as a "derivative work"? If not, are there any ways to avoid it?

  • 1
    There is one very simple way to avoid it becoming a derivative of a library: don't use it. Jul 4 '20 at 0:28
  • 1
    I am sure this question is a duplicate. And I am sure that the answer is yes. If you don't modify the GPL code, then you are only using it. This disables about 90% of the license (until it is modified, then the rest applies to who ever modifies it). You do still have to provide the library in source form (preferred form for editing: not minified, or obfuscated. You can minify but have to also provide access to preferred form, add a footnote about its use, and the download link. ) Jul 4 '20 at 9:19
  • 1
    @ctrl-alt-delor You also have to license the entire derivative work as GPL, if this counts as a derivative work. That's kinda important.
    – user253751
    Jul 7 '20 at 9:58
  • @user253751 the question is "is this a derivative work?" Jul 8 '20 at 6:25
  • @ctrl-alt-delor because of the way I phrased the question, it's "is this not a derivative work" -> is that what you answered yes to?
    – atomh33ls
    Jul 8 '20 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.