OSS License compatibility question

[Ashley123456789]

Feature description

There’s some possible confusion on the license of your repository when you combine other open-source code.

The module project_euler claims its license as CC BY-NC-SA 4.0 in README.md. However, the license of your whole project is showed as the MIT license in LICENSE.md, i.e., less strict than CC BY-NC-SA 4.0 on license terms, which has impacted the whole license compatibility in your repository and may bring legal and financial risks.

You can select another proper license for your repository, or write a custom license with license exception if some license terms couldn’t be summed up consistently

[Preetiraj3697]

In your specific case, the project_euler module is licensed under CC BY-NC-SA 4.0, which is a more restrictive license than the MIT license that your repository is using. This means that if you use the project_euler module in your repository, you may need to comply with the terms of the CC BY-NC-SA 4.0 license, which includes giving attribution to the original author, not using the code for commercial purposes, and sharing any modifications under the same license.

To avoid any confusion or legal issues, you could either choose a license for your entire repository that is compatible with the CC BY-NC-SA 4.0 license, or you could write a custom license with a license exception that specifically addresses the use of the project_euler module in your repository. It may also be helpful to consult with a legal expert who is familiar with open-source licensing.