Read on Twitter
Want to see something cool around @NuGet? Well this is the thread for you. I setup an @elastic #kibana dashboard to look at data and here is what I found. Cc @maartenballiauw and @dotnetfdn
Thread starting… the timeframe is the last 30 days.
Thread starting… the timeframe is the last 30 days.
22, 531 unique packages were published to NuGet.
The publishing frequency is pretty stable, likely because of CI pipelines publishing on intervals.
Top Package Authors include Microsoft, SyncFusion, Google, and Amazon.
Target frameworks netcoreapp3.1 and net standard 2.1 are common while other target frameworks seem to be minimal
MIT and No License comprise the biggest licenses in our ecosystem.
Popular tags include AWS, rocket, aiwins, cloud, amazon, Xamarin, sync fusion, .net, core, ump, and aspnetcore
5,280 of those packages target netcoreap3.1
Amazon targeting netcoreapp3.1 aggressively, and we see some human names when filtering by netcoreapp3.1.
43 of those packages are Tizen40 packages.
Unsurprisingly, these packages are for mobile library MvvmCross.
3,350 of those packages target netstandard2.1.
Out of the packages that target netstandard2.1, here are the other target frameworks they also target and how frequently they publish.
2,235 packages target net45 with Google, Tencent, Amazon, and Syncfusion.
The devs at @jetbrains has published 22 packages in the last 30 days. With tags like console, dotmemory, leak, profiling, resharper, and rider.
5,024 packages in the last 30 days are published under the MIT license.
The @dotnetfdn accounts for 5.44% of those packages being published, while Microsoft tops out at 42.23%.
The @dotnetfdn has published 101 packages with a sporadic publishing frequency. Projects include MvvmCross, @ReactiveXUI , Splat, Pharmacist, Akavache (using package prefix)
8 packages were published that target “wp8” which is Windows Phone 8.
Keep hope alive!
Keep hope alive!
276 packages are tagged with SQL
Over the last 6 years, we can see netstandard2.0 take off in the middle of 2017. Seems like the community just went for it as the defacato option.
Netcoreapp3.1 adoption spiked at the beginning of this year, but still relatively low compared to the easy upgrade path.
Netcoreapp3.1 adoption spiked at the beginning of this year, but still relatively low compared to the easy upgrade path.
