Contents
Do all packages in NuGet have free licence to use?
A NuGet package available on nuget.org can have any license. There is no restriction on whether the NuGet package is free, open source or commercially licensed. You should review the license that each NuGet package has.
Where can I get license information for a package?
Basically you can use the Get-Package cmdlet to get a list of packages referenced in a specific project (or in an entire Solution). Regarding the license information for each package, for what I’ve seen you can only get the license URL and not just a short string representing the license type.
Do you need a license for all dependencies?
If you don’t want to confuse package users make sure that all dependencies (both immediate and transitive) have compatible licenses with your package license. Typically dependency licenses should be more permissive or the same level of permissive as your package license.
Do you have to have a license for linking?
Linking will be performed by an app developer who will use your package on a build or run stage. If you don’t want to confuse package users make sure that all dependencies (both immediate and transitive) have compatible licenses with your package license.
How does licenses.nuget.org respond to HTTP 200 status code?
Licenses.nuget.org responds to requests containing valid license expressions with an HTTP 200 status code and a web page containing a description of the license expression: if supplied license expression contains a single license identifier a web page is returned that contains that license reference text;
Is there a machine readable version of licenses.nuget?
Licenses.nuget.org is intended to be viewed by people in their browsers, no machine-readable responses are provided. HTTPS protocol must be used and requests are expected to be constructed in a certain way.
Is the URL to licenses.nuget.org case sensitive?
Please note, that all elements of license expressions are case sensitive, and therefore all input to licenses.nuget.org is case sensitive as well. License expressions (including the trivial cases when expression consists of a single license) have to be URL-encoded and used as a path in the request to licenses.nuget.org.