The other day I was discussing the open source dependencies we had in a project with a lawyer. Forgetting my IANAL (I am not a lawyer) status, I made some bold statement regarding our legal obligations, or lack thereof, with respect to the licenses.
I can just see her rolling her eyes and thinking to herself, "ORLY?" She patiently and kindly asked if I could produce a list of all the licenses in the project.
Groan! This means I need to look at every package in the solution and then either open the package and look for the license URL in the
metadata, or I need to search for each package and find the license on NuGet.org
If only the original creators of NuGet exposed the package metadata in a structured manner. If only they had the foresight to provide that information in a scriptable fashion.
Then it dawned on me. Hey! I'm one of those people! And that's exactly what we did! I bet I could programmatically access this information. So I immediately opened up the Package Manager Console in Visual Studio and cranked out a PowerShell script...HA HA HA! Just kidding. I, being the lazy ass I am, turned to Google...(Read whole news on source site)