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

The package.json license field does not reflect LICENSE-MIT #88

Closed
SmileyJames opened this issue Feb 4, 2021 · 1 comment
Closed

The package.json license field does not reflect LICENSE-MIT #88

SmileyJames opened this issue Feb 4, 2021 · 1 comment

Comments

@SmileyJames
Copy link

this
"license": "(MIT OR GPL-3.0)",
https://github.com/nbubna/store/blob/master/package.json#L32

seems at odds with:
https://github.com/nbubna/store/blob/master/LICENSE-MIT

GPL 3 is very different to MIT, it is copyleft
https://www.gnu.org/licenses/gpl-3.0.en.html

@nbubna
Copy link
Owner

nbubna commented Feb 4, 2021

Since you probably closed this because you found the answer, this is redundant for you. But in case others wonder, the answer is that as creator I (and ESHA) can provide the software under any number of licenses we choose. In a lot of ways, specifying both GPL 3 and MIT seems contradictory, but the intent is to offer this under the "do whatever you want, as long as we're not liable" plan so you can use this in any stack, without legal considerations.

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

No branches or pull requests

2 participants