Developers need LICENSE files for code reuse
16 posts in the last 30 days, all from GitHub.
“Hello, Thank you for sharing your project on GitHub! I noticed that this repository does not currently have a license specified. Adding a license is important because: 1. Clarity on Usage : Without a license, others cannot legally use, modify, or share your code, as the default…”
“Hi! First, thanks for the fantastic work on the FRC design course and the Onshape part libraries — they've been a huge help to our team. You describe the project as open source (a goal I fully agree with), but the active repos (FRCDesign.org and FRCDesignApp) don't have a…”
“Thank you for publishing AnalogCoder Pro alongside the TCAD 2026 paper. As with the original AnalogCoder repository (issue filed there as well), this repository has no LICENSE file and GitHub reports no license for it. Under default copyright that makes the code, sample designs…”
Multiple developers are requesting the addition of `LICENSE` files to repositories, as their absence restricts legal use and adaptation of the code by others. This limits collaboration and open-source contributions.
SOURCES (19)
“Hello, Thank you for sharing your project on GitHub! I noticed that this repository does not currently have a license specified. Adding a license is important because: 1. Clarity on Usage : Without a license, others cannot legally use, modify, or share your code, as…”
Please add a license file so others may understand the guidelines for derivative work. Thanks!
“Hello Waveshare team, This repository has no licence file, so the example code (for instance components/epaper driver bsp and audio bsp ) is all rights reserved by default and can't be reused in open source projects. I'm building open source firmware for the ESP32 S3 ePaper 1.54 (a desk pager for AI coding agents, to be contributed to an MIT licensed project) and had to switch to Espressif's drivers instead of your examples for that reason. Would you consider adding an open source licence such a”
Hi @wiomoc! Thanks for sharing this repository. I found your code very interesting and would love to use it, but noticed that the project currently doesn't have a license file. Without an…
Thank you for making this code available! Please add an open source license if you do intend for it to be open source. Thanks!
Thanks for releasing MemoryArena (arXiv 2602.16313). The repository has no LICENSE file and GitHub detects no licence, so we can't tell whether we may reuse it. Could you say which licence covers…
“Even the paper said we can you openly the model, we need a free license attached to the github. Can you add one please.”
This project is cool. Thank you. But it needs a license.
“Hi! First, thanks for the fantastic work on the FRC design course and the Onshape part libraries — they've been a huge help to our team. You describe the project as open source (a goal I fully agree with), but the active repos (FRCDesign.org and FRCDesignApp) don't have a LICENSE file. Without one, the default legal position is "all rights reserved" — so teams can't safely reuse, adapt, or redistribute the content in their own tools and robot projects, even though that's clearly the intent. Woul”
“Hi @mtrdrgz, First of all, thank you for sharing this amazing project! I noticed that the repository currently doesn't have a LICENSE file or any license specified in the README. According to GitHub's default terms, this means "all rights reserved," which prevents others from legally contributing, modifying, or using the code for their own projects. Would you consider adding an open source license (such as MIT, GPL, or Apache 2.0) to this project? This would clarify how the community can interac”
Could you add a LICENSE file so others know how they're allowed to use and reuse this project? Thanks!
“The README says the component is based on work by Andriy Malyshenko (sonocotta) licensed under GPL 3.0, but the repository itself has no LICENSE file, so the terms for this repository are not stated explicitly. Could you add one? If it is GPL 3.0, it would also help to say whether it is "GPL 3.0 only" or "GPL 3.0 or later" (the standard notice "either version 3 of the License, or (at your option) any later version" decides that). Background: I use the component in an open hardware project (a dro”
“please add a LICENSE. something like BSD or MIT would work best for this project. this looks really cool! I always love RISCV stuff”
Cool project! Thank you for sharing. Please add a LICENSE file.
Team, Our organization would like to use your code. The lack of a license, however, means we can't determine what terms you allow for the use of your code. Can you please…
“Hi, We are interested in using and contributing to VLA JEPA, but I could not find a license covering the repository code. Could you please confirm the intended license and, if appropriate, add the corresponding LICENSE file to the repository? Thanks for your help!”
Hi @sting8k — could you please add an explicit license file and package metadata for pi vcc? I am evaluating v0.7.2 for use and may need to adapt the benchmark/integration code locally.…
“Thank you for publishing AnalogCoder Pro alongside the TCAD 2026 paper. As with the original AnalogCoder repository (issue filed there as well), this repository has no LICENSE file and GitHub reports no license for it. Under default copyright that makes the code, sample designs, and benchmark all rights reserved, so downstream projects cannot legally reuse or adapt any of it, and cannot cite the repository as an open source. Would you consider adding an explicit license? MIT, BSD 3 Clause, or Ap”
“Thank you for publishing AnalogCoder alongside the AAAI 2025 paper — the feedback enhanced loop and the operating point checks are genuinely useful reference material. The repository currently has no LICENSE file, and GitHub reports no license for it. Under default copyright that means the code, subcircuit library, and benchmark are all rights reserved, so downstream projects cannot legally reuse, adapt, or even vendor small parts of them, and cannot cite the repository as an open source in thei”