3 ms·
I was curious how this handled repositories that use are offered under more than one license, so I tried this out on the Rust repository: "license": { "k
by kibwen 12y ago
I was curious how this handled repositories that use are offered under more than one license, so I tried this out on the Rust repository:
"license": {
"key": "apache-2.0",
"name": "Apache License 2.0",
"url": "https://api.github.com/licenses/apache-2.0"
}
Rust is offered under both MIT and Apache 2, and has corresponding LICENSE-MIT and LICENSE-APACHE files in its root directory. I'm assuming that Github simply searches alphabetically for all files that begin with LICEN[CS]E and eagerly terminates upon finding a single match.
- yaeger 12y agoThat would be very bad for projects that not only use dual licenses but especially if one of them is a commercial license. If you just checked there and found the apache and think "Great, I can put that into my closed source tool" you might be in for a surprise when the author contacts you and tells you that the apache is only for non commercial use and there is a second, paid license for commercial use available that you should have taken.
- delsalk 12y agoSurely doing that would require them to rewrite the Apache license (thus making it no longer the apache license) otherwise there's no legal way of enforcing the non-commercial use?