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
The terms of the MIT license indicate that the license itself must be distributed with any significant portions of the code. Unfortunately, I don't see a LICENSE, LICENSE.txt, LICENSE.md nor any other source of the MIT license in your project.
I appreciate your work and I like that it seems that this library is being released under a MIT license, but currently it is legally ambiguous and that's potentially a hazard with using the tools. Would you be willing to add a file with the license or place the license at the top of your library?
The text was updated successfully, but these errors were encountered:
Hello @fidian! Thank you for feedback. I'm not very familiar with licence things and prefer WTFPL licence. But if you know how it should be defined to be legal — feel free to make pull request! I will be glad to merge it!
You need to update your package.json to say WTFPL, then include a copy of the license as LICENSE, LICENSE.txt, LICENSE.md or a similar name. Currently you cite MIT, but WTFPL is great too. I'm just hoping it is a bit more explicit so I am able to use this software without the potential for license issues.
The terms of the MIT license indicate that the license itself must be distributed with any significant portions of the code. Unfortunately, I don't see a
LICENSE
,LICENSE.txt
,LICENSE.md
nor any other source of the MIT license in your project.Additionally, citing
MIT © Shuvalov Anton
isn't quite the same as sayingCopyright © 2016 Shuvalov Anton, Licensed under a MIT License
and the latter wording is significantly more correct.I appreciate your work and I like that it seems that this library is being released under a MIT license, but currently it is legally ambiguous and that's potentially a hazard with using the tools. Would you be willing to add a file with the license or place the license at the top of your library?
The text was updated successfully, but these errors were encountered: