You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Cyril, I was researching some of your very useful image-optimisation related repos and discovered a possible licensing problem. I'm sorry to be the bearer of bad news, but it looks like the @wasm-codecs/gifsicle package published to npm contains a compiled, binary form of the GPL gifsicle.
Whilst the code in this repo can remain MIT-licensed, the combined work should be considered GPL-2.0 as it runs in the same process. With the usual "I am not a lawyer" proviso, I think this means the license field should be set to GPL-2.0 as this is what is published to npm.
Any packages depending upon @wasm-codecs/gifsicle that run in the same Node.js process are likely to be equally affected.
The text was updated successfully, but these errors were encountered:
Hi Cyril, I was researching some of your very useful image-optimisation related repos and discovered a possible licensing problem. I'm sorry to be the bearer of bad news, but it looks like the
@wasm-codecs/gifsicle
package published to npm contains a compiled, binary form of the GPL gifsicle.Whilst the code in this repo can remain MIT-licensed, the combined work should be considered GPL-2.0 as it runs in the same process. With the usual "I am not a lawyer" proviso, I think this means the license field should be set to
GPL-2.0
as this is what is published to npm.Any packages depending upon
@wasm-codecs/gifsicle
that run in the same Node.js process are likely to be equally affected.The text was updated successfully, but these errors were encountered: