Skip to content

Potential Inconsistencies Between Repo and Model License #72

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

Open
yueyangchen1 opened this issue May 14, 2025 · 0 comments
Open

Potential Inconsistencies Between Repo and Model License #72

yueyangchen1 opened this issue May 14, 2025 · 0 comments

Comments

@yueyangchen1
Copy link

Hi, while reviewing the licenses for this repository and the model it depends on, I noticed a potential inconsistency that could cause confusion or legal risks in some situations.

Your repository uses the model meta-llama/Llama-2-7b-hf at scripts/prepare_datasets/label_data_2.py, which is licensed under llama2. Meanwhile, your repository itself is licensed under MIT.

These two licenses have key differences that could lead to confusion:
1.The LLaMA 2 license includes the requirement: "You must retain in all copies of the Llama Materials that you distribute the following attribution notice within a “Notice” text file distributed as a part of such copies: “Meta Llama 3 is licensed under the Meta Llama 3 Community License, Copyright © Meta Platforms, Inc. All Rights Reserved.”"However, your repository license mit does not mention this, and therefore has no such requirement.

As a result, developers might not realize they need to include a Notice file when modifying or distributing the repository, which could unintentionally lead to non-compliance with the model license.

2.The LLaMA 2 license also includes: "You will indemnify and hold harmless Meta from and against any claim by any third party arising out of or related to your use or distribution of the Llama Materials." but mit license does not mention this.

Without knowing this, developers might assume they’re not personally responsible for any issues arising from the use of the model, which could lead to unexpected risks.

Suggested Actions:
1.You might consider adding a brief note in the README, LICENSE, or a separate NOTICE file to clarify the model’s license requirements (e.g., attribution).
2.It could be helpful to include a reference to the model license and summarize any key obligations, so developers are aware of them.
3.You may want to gently remind users that, in some cases, they should check both the repository license and the model license, especially when redistributing or modifying the model.

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

1 participant