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
There’s possible confusion on the license of your repository when you combine other open-source code.
The modules opennre/tokenization/word_piece_tokenizer.py, opennre/tokenization/word_tokenizer.py, opennre/tokenization/basic_tokenizer.py, and opennre/tokenization/bert_tokenizer.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
The text was updated successfully, but these errors were encountered:
There’s possible confusion on the license of your repository when you combine other open-source code.
The modules
opennre/tokenization/word_piece_tokenizer.py
,opennre/tokenization/word_tokenizer.py
,opennre/tokenization/basic_tokenizer.py
, andopennre/tokenization/bert_tokenizer.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:
The text was updated successfully, but these errors were encountered: