The 1st Billion
Today, NuGet.org reached one billion downloads. This is a momentous achievement for our users and the community of package authors who continue to use and build new libraries that is the cornerstone of .NET adoption. We want to take this opportunity to give a huge thank you to the millions of our users who made this milestone possible. With the advent of .NET Core, ASP.NET Core, Universal Windows Apps, open sourcing of the Xamarin Platform, and the accelerated use of NuGet, we believe we will hit the next 1 billion in a year or so.
Journey to 1 Billion
NuGet started out as the NuPack project which was then renamed to NuGet and accepted into the ASP.NET Open Source Gallery by the OuterCurve foundation. This was one of the first forays by Microsoft into Open Source development and we are proud of that heritage. For a taste of nostalgia, here are some of the very first posts around the NuGet project: Scott Guthrie, Phil Haack, Scott Hanselman and Mary J Foley
Here are some fun stats around our growth over the last 6 years. Data from the past 6 weeks or so across some of these dimensions are available in our statistics page in NuGet.org.
Downloads in NuGet.org grew almost 80% this year. From an all time download count of 50 million in 2013, we now average around 72 million downloads per month in 2016. NuGet from a day 1 was built with caching in mind and we have seen significant usage of NuGet via NuGet Server, VSTS Package Management, myget, ProGet, Nexus, Artifactory and other third party services. These download numbers purely represent downloads from NuGet.org. We suspect the actual downloads of NuGet packages to be a much higher number.
If you were curious which was the billion’th package that was downloaded. The magic number was taken by the dnx-clr-win-x86 package, which was downloaded at around 3:15 a.m (PST) on 5/10/2016.
We have over 54K unique packages in NuGet.org and over 600K packages in total. Year over year we are seeing around 31% growth in the number of packages being uploaded to NuGet.org.
This visualization shows the average count of requests from NuGet v3 client, the Windows x86 Command line and the .NET CLI NuGet Client over the last 2 weeks to NuGet.org endpoints. As you can see, there is huge interest in .NET Cross platform tools and we believe this is going to be a significant part of our tools traffic going forward.
We now have around 600K users visiting NuGet.org on a monthly basis to search and peruse our packages. We are making investments in improving search and package information in the near future to make user engagement much more meaningful on the website.
An Open Source project thrives and survives on the patronage of its users. Even from the very early days, we have had significant contributions from the community. 3 out of the top ten contributors in the initial days were individuals from the community. Fast forwarding to today, we have over 130 contributors on GitHub across NuGet.Client and NuGetGallery. While a number of these folks are MSFT’s, there is a large number of contributions from the community as well. We are always on the lookout for folks from the community to suggest ideas, and contribute features to the project.
Among non-Microsoft packages. Json.net authored by our friend James Newton-King reigns supreme with over 28 million downloads. Our most prolific author/owner with the largest number of packages at this time is Definitely Typed which curates high quality TypeScript definitions with over 1,779 packages.
We cannot reiterate enough how much our community means to us and we want to continue to partner with you all to innovate and push the boundaries of package management with NuGet.
Why you should be using NuGet
There is a lot of innovation happening in the community around .NET which enables you to develop software faster than ever. NuGet is the most widely adopted system across the community for consuming shared components and is the primarily channel for showcasing this innovation. One of the big goals for us is to optimize developer productivity, reduce redundancy and promote code-reuse. Using NuGet Packages is one the most optimal ways to do this. We are here to help you succeed in adopting NuGet and if you would like to talk to us about how NuGet can help you achieve these goals, do not hesitate to reach out to us at firstname.lastname@example.org or holler at us on Twitter @nuget.
We want to hear your feedback!
We want NuGet to meet the evolving needs of our community. If you would like share your pain points and your current and future needs, use the calendly link to set up a quick 15-30 min call with us. If you would like to send us an email instead, hit us up at email@example.com. You can also leave a comment below, and as always, if you run into any issues or have an idea, open an issue on GitHub.