Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ramifications of Webassembly GPLv2 license? #7229

Closed
mtraynham opened this issue May 7, 2018 · 9 comments · Fixed by #7245
Closed

Ramifications of Webassembly GPLv2 license? #7229

mtraynham opened this issue May 7, 2018 · 9 comments · Fixed by #7245

Comments

@mtraynham
Copy link

mtraynham commented May 7, 2018

I tried a simple upgrade to Webpack 4.8 and my license checker found the new Webpack version has pulled in the WebassemblyJS code which is licensed under GPLv2. I'm not a lawyer or anything, but is this safe to use?

Seems like it requires all code using this library to be licensed under GPLv2 as well, but as I said, I'm not a lawyer, so I don't really know.

@mohsen1
Copy link
Contributor

mohsen1 commented May 8, 2018

@sokra @TheLarkInn this is important

@xtuc
Copy link
Member

xtuc commented May 8, 2018

What's the correct license to use? MIT?

@sokra
Copy link
Member

sokra commented May 8, 2018

MIT would be great

@sokra
Copy link
Member

sokra commented May 8, 2018

@mtraynham I'm not a lawyer, but I guess it safe to use this as long you don't ship these code within your application (which webpack doesn't do).

@mtraynham
Copy link
Author

mtraynham commented May 8, 2018

Gotcha. I'm just a bit uneasy about the copyleft aspect of GPL and exactly what a derivation means, but you're probably right. It would be great to stick to a permissive free license, such as MIT, Apache or BSD, which doesn't have a copyleft aspect to it. That way, I don't even have to wonder if this is a problem 😄

@TheLarkInn
Copy link
Member

TheLarkInn commented May 8, 2018 via email

@montogeek
Copy link
Member

@xtuc
Copy link
Member

xtuc commented May 8, 2018

It's me, I'll change it.

@mtraynham
Copy link
Author

Thanks guys, much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants