Introduction

Over the last six months, the NuGet team has been busy running user surveys for NuGet and the .NET ecosystem. Recently, our team launched our first quarterly user survey for NuGet.org. With over 500 responses, we wanted to spend some time to share with you what we’ve learned in these last few months.
The post State of the NuGet Ecosystem appeared first on The NuGet Blog.

Action required: If you validate that packages are repository signed by NuGet.org using a NuGet client policy, NuGet.exe verify command, or the dotnet nuget verify command, please follow these steps by March 15th, 2021 to avoid potential disruptions when installing new NuGet.org packages.
The post The NuGet.org repository signing certificate will be updated as soon as March 15th, 2021 appeared first on The NuGet Blog.

We are excited to announce that NuGet.org now supports one of our top customer asks – advanced search! You can now use a multitude of sorting and filtering criteria to help find the best NuGet packages for your needs!

What’s new?
The post Advanced search on NuGet.org appeared first on The NuGet Blog.

Last November, we shared our two-stage plan for deprecating TLS 1.0/1.1 on NuGet.org in which we stated that the permanent removal of TLS 1.0/1.1 support would occur in April 2020. However, in April, to avoid disrupting customers in the midst of the COVID-19 pandemic,
The post NuGet.org will permanently remove support for TLS 1.0 and 1.1 on June 15th appeared first on The NuGet Blog.

Last November, we shared our two-stage plan for deprecating TLS 1.0/1.1 on NuGet.org and actions you can take today to ensure your systems use TLS 1.2. In this post, we will go into more details and a specific timeline for Stage 1 i.e.
The post Deprecating TLS 1.0 and 1.1 on NuGet.org – Stage 1 appeared first on The NuGet Blog.

co-authored by Scott Bommarito

At Microsoft, using the latest and secure encryption techniques is very important to us to ensure the security and privacy of our customers. TLS 1.0 and TLS 1.1, released in 1999 and 2006 respectively, are known to be vulnerable to a number of attacks including POODLE and BEAST.
The post Deprecating TLS 1.0 and 1.1 on NuGet.org appeared first on The NuGet Blog.

It’s been a long time coming, and today we are excited to announce the new and improved search on NuGet.org leveraging Azure Search. We want to start this post with a huge thanks to you, the NuGet community, for providing feedback.
The post New and improved NuGet Search is here! appeared first on The NuGet Blog.

There are several criteria you can use today to evaluate NuGet packages. We received feedback that you would like even more information to help choose the right packages. We’re excited to introduce GitHub Usage on nuget.org, which allows you to explore top GitHub repositories that depend on the package you are looking at.
The post Surfacing GitHub Usage for packages on NuGet.org appeared first on The NuGet Blog.

We published our last NuGet roadmap in June last year. Many of the features announced were major additions to NuGet and we have been hard at work to implement those over the last few months. In this post, we will start by summarizing the features we have completed and then peek into the next wave of work planned.
The post NuGet Spring 2019 Roadmap appeared first on The NuGet Blog.

With PackageReference, NuGet always tries to produce the same closure of package dependencies if the input package reference list has not changed. However, there are a few scenarios where it may not be able to do so. While these cases are limited,
The post Enable repeatable package restores using a lock file appeared first on The NuGet Blog.

For the past several months we have focused on various features to improve package security and trust. Around a year back, we had announced our plans on various signing functionalities that we have been implementing at a steady pace. We enabled package author signing and NuGet.org repository signing earlier this year.
The post Lock down your dependencies using configurable trust policies appeared first on The NuGet Blog.

Starting today, you can publish symbol packages to the NuGet.org symbol server. With NuGet.org as a single service provider for libraries and symbols, package authors and consumers will have a streamlined publishing and consumption experience. With a single place for managing authentication and identity,
The post Improved package debugging experience with the NuGet.org symbol server appeared first on The NuGet Blog.

NuGet.org now supports surfacing source code repository link for NuGet packages. This will enable package authors to surface both the project’s website and the source repository using the projectUrl and the repository properties respectively instead of having to choose between the two using just the projectUrl property.
The post Introducing Source Code Link for NuGet packages appeared first on The NuGet Blog.