[toast0]

Well, does that allow you to have the rest of your backend GPL licensed and simply not distributed? Nobody has a right to see the code unless they have the executable, and you're not giving anyone the executable, so...

Kind of unfortunate if there's a leak though.

[cwillu]

A leak of an executable doesn't imply a requirement to provide source anymore than a theft implies a warranty.

[toast0]

I meant a leak of the source code, not the executable. If the source code comes with a license that was intentionally applied by the copyright holder, does it matter that it wasn't intended to be released if the license allows for general use?

[cwillu]

If I make changes to a GPL3 library, but never distribute it, and you come along and leak it, you've distributed my changes without a license. Those changes are toxic, and the result cannot be distributed by anyone. It's not really any different than the usual dance one has to perform to combine two components with incompatible licenses: you can mix the ingredients yourself, you can tell people how to mix the ingredients themselves, but you can't distribute the cake.