Skip to content
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

Pypi ultralytics-yolov5 uses Apache but this repo uses AGPL #13509

Open
1 task done
protonphoton opened this issue Feb 12, 2025 · 5 comments
Open
1 task done

Pypi ultralytics-yolov5 uses Apache but this repo uses AGPL #13509

protonphoton opened this issue Feb 12, 2025 · 5 comments
Labels
question Further information is requested

Comments

@protonphoton
Copy link

Search before asking

Question

Hello, I am recently trying out your yolov5 model but have some issues with your licensing. In this repo, clearly you are using AGPL but from your pypi package: https://pypi.org/project/ultralytics-yolov5/ , you have an Apache license. Does that mean as long as I am using the pypi package, I am not restricted by AGPL? If not, would you please update your license so we don't end up with license confusion? Thank you so much!

Additional

No response

@protonphoton protonphoton added the question Further information is requested label Feb 12, 2025
@pderrenger
Copy link
Member

@ranranproton thanks for catching that! The AGPL-3.0 license applies to all Ultralytics YOLOv5 software and models as stated in our LICENSE file. The PyPI metadata has been corrected to reflect AGPL-3.0. For commercial licensing options that avoid AGPL requirements, see Ultralytics Licensing. We appreciate your diligence!

@protonphoton
Copy link
Author

Thanks @pderrenger . I have another question. If we started using yolov5 before there was even AGPL license couple years ago, should we change our license to AGPL or we can keep our previouse license?

@pderrenger
Copy link
Member

@protonphoton if your usage commenced prior to the establishment of the AGPL-3.0 license and you have not updated to a version with AGPL-3.0, then your usage is governed by the terms that existed at that point, but any updates you make now would fall under AGPL-3.0 or require an Ultralytics Enterprise License.

@protonphoton
Copy link
Author

@pderrenger , thanks for the confirmation. I checked with the Pypi yolov5 package and it is still under Apache, and the last update is 2022. So does that mean as long as I keep using this version of package, the usage will be under Apache?

@pderrenger
Copy link
Member

@protonphoton Correct, usage rights are defined by the license in effect at the time of software acquisition, so if you obtained ultralytics-yolov5 package under the Apache license before it was updated, that license would apply, but any updates after the license change to AGPL-3.0 would be subject to the new license, or require an Ultralytics Enterprise License.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants