There’s possible confusion on the license of your repository when you combine other open-source code.
The modulessecond/builder/dataset_builder.py, second/pytorch/builder/lr_scheduler_builder.py, second/pytorch/builder/optimizer_builder.py and second/pytorch/builder/input_reader_builder.py claim their licenses as Apache-2.0.
However, the license of your whole project is shown as the MIT license in LICENSE, i.e., less strict than Apache-2.0 on license terms, which may impact the whole license compatibility in your repository, thus confusing subsequent users and bringing possible legal and financial risks.
If possible, you can fix them in one of the following ways:
select another proper license for your repository, e.g., Apache-2.0
update this license with term exceptions added for specific modules
remove these modules if they are not actually useful
There’s possible confusion on the license of your repository when you combine other open-source code.
The modules
second/builder/dataset_builder.py,second/pytorch/builder/lr_scheduler_builder.py,second/pytorch/builder/optimizer_builder.pyandsecond/pytorch/builder/input_reader_builder.pyclaim their licenses as Apache-2.0. However, the license of your whole project is shown as the MIT license in LICENSE, i.e., less strict than Apache-2.0 on license terms, which may impact the whole license compatibility in your repository, thus confusing subsequent users and bringing possible legal and financial risks.If possible, you can fix them in one of the following ways: