shouldiuse.io

Report

Should I Use NuGet Gallery?

nuget.org·Analyzed 18 hours ago··Based on 10 sources

The central package repository for NuGet, the package manager for .NET.

Depends

Depends

Nothing to buy: if you build .NET, this is the default public package registry and you simply use it.

Free public package registry for .NET — essential if you build .NET; irrelevant if you don't; wrong tool for private feeds.

Confidence: Medium

Free

Cost

Public registry, no paid plan

2011

Gallery launched

Per Microsoft .NET Blog

2

CVEs on the Gallery

2024 input flaw, 2026 critical RCE

Value for money5

Free public infrastructure; nothing to purchase.

Ease of use4

Built into Visual Studio and dotnet CLI tooling.

Feature depth4

Automatic dependency handling, rich public metadata API.

Support quality3

FAQ, status page, GitHub issues; no paid support.

Security posture2

Critical 2026 RCE CVE plus active typosquatting pressure.

Pros

  • Default, central package repository for all .NET authors and consumers¹
  • Automatically handles package dependencies
  • Open-source manager streamlines integrating third-party libraries into projects³
  • Public API exposes versions, downloads, authors, licenses, and tags

Cons

  • July 2025 mass package-deletion incident disrupted publishers
  • 2026 critical RCE vulnerability in the gallery backend
  • Active typosquatting and supply-chain attack concerns
  • No private feeds — you need ProGet, MyGet, or Artifactory

Gotchas

  • highTyposquatting and dependency-confusion attacks are rising; double-check exact package names before installing.
  • highCVE-2026-39399: critical RCE in the gallery's .nuspec handling; watch the status page.
  • mediumJuly 2025: Microsoft packages were deleted; team says operator error, not a breach. Keep local mirrors.
  • mediumPublic registry only: internal packages require a separate private feed product — extra cost and setup.

Best for

  • .NET/C# developers
  • Open-source library publishers
  • Teams consuming third-party .NET packages

Not for

  • Anyone needing private or internal package hosting
  • stacks (npm, PyPI, Maven users)
  • Buyers wanting vendor support, SLAs, or contracts
  • Security teams wanting built-in package vulnerability scanning

Companies that use it

  • Microsoft²
  • QuestPDF²
  • Iron Software
  • uSkinned Site Builder

Pricing

Free tier: Yes

Security

Two CVEs against the Gallery itself (2024 input flaw, 2026 critical RCE), rising typosquatting pressure; the 2025 deletion incident was officially not a breach.

  • CVE-2026-39399 — critical RCECritical vulnerability in the NuGet Gallery backend job's handling of .nuspec files inside packages.
  • CVE-2024-47604 — input neutralization flawImproper neutralization of input in the NuGetGallery's handling of HTML element attributes.
  • July 2025 package deletionsMicrosoft-published packages were removed; post-mortem attributes it to operator error, not a breach or external attack.

What users say

Users treat NuGet.org as indispensable .NET infrastructure, but the 2025 package-deletion incident and supply-chain chatter eroded some trust.

There seems to be an ongoing supply chain attack or suspicious activity on NuGet.org
Reddit, r/dotnet
Someone suggested a thread on the NuGet home discussions about this, so I made one
Reddit, r/dotnet

Alternatives

Compare NuGet Gallery with each alternative.

ProGet

Self-hosted private NuGet feed server; strong mid-market option.

Full analysis

Based on ~30 public sources; user-review depth is thin and no numeric review ratings for the Gallery itself were found.

Sources

  1. official
  2. official
  3. review
  4. review
  5. review
  6. security
  7. security
  8. official
  9. news
  10. news

Rate this review

Anonymous. You can change your vote.

Loading votes…

Ask a follow-up

Ask if a use case fits. Answers stay inside this report and its sources.

    Comments

    One queue. No replies. Give a display name first. Limit: 7 comments per day.

    Save a name to write a comment.

    No comments yet.