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

Confusing License Specified in Repository #5

Open
ghost opened this issue May 29, 2016 · 0 comments
Open

Confusing License Specified in Repository #5

ghost opened this issue May 29, 2016 · 0 comments

Comments

@ghost
Copy link

ghost commented May 29, 2016

There is no clear license specified in this repository (neither a LICENSE.md file, nor a License section in the README.md file). However, in the package.json file, the "license" field is set to "ISC". But at the same time, there is no actual ISC license text anywhere in the repository. Even the "author" field in the package.json file is set to an empty string. There may be certain legal issues with the license defined in such an ambiguous way, both for the author (@samerbuna) and for anyone who wants to use any part of this code.

If you don't include any license, U.S. copyright law states that the most restrictive copyright terms apply (meaning "All Rights Reserved"), which means that no one can legally reuse, share, and/or modify any part of this code. The fact that the "ISC" license is specified in package.json, but there is no ISC license text anywhere creates a very confusing and ambiguous situation as to whether or not the ISC license applies.

Can you please properly, clearly, and consistently define what type of license you want this code to be released under within this repository (preferably as a LICENSE.md file)? Thanks.

@samerbuna

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

0 participants