Show HN: Simple modenized .NET NuGet server reached RC

24 kekyo 13 9/1/2025, 2:00:26 PM github.com ↗
A simple .NET NuGet server implementation built on Node.js that provides essential NuGet v3 API endpoints.

Key Features:

* Easy setup, run NuGet server in 10 seconds! * NuGet V3 API compatibility: Support for modern NuGet client operations * No need database management: Store package file and nuspecs into filesystem directly, feel free any database managements * Package publish: Flexible client to upload .nupkg files via HTTP POST using cURL and others * Basic authentication: Setup authentication for publish and general access when you want it * Reverse proxy support: Configurable trusted reverse proxy handling for proper URL resolution * Modern Web UI with enhanced features. * Package importer: Included package importer from existing NuGet server * Docker image available

Comments (13)

shashasha2 · 6h ago
> A simple NuGet server implementation built on Node.js that provides essential NuGet v3 API endpoints

Why not build on .NET ?

mhh__ · 2h ago
Maybe there's a lesson there. It's quite difficult to be spontaneous in dotnet (i'm not just being snippy I can immediately tell a story in my head about starting doing this in F# or C# and then bailing and doing it in an hour in a different language)
mrsmrtss · 24m ago
Sorry, but there is absolutely nothing you gain with Node.js here in server side at least, it's clearly inferior choice for this job. You loose performance, type safety and in about two weeks there are hundreds of security issues found in your dependencies etc. Looking at the code, there are also clear security red flags for me and also the error handling is not to my taste, but that is not related to the tech. Maybe he wanted to use same language for the backe-end and front-end, but I think it's not a good argument here.
oaiey · 6h ago
Simple question: why code it in nodejs if .net core is more than capable of running it?
Kwpolska · 4h ago
Packaging tools for language/ecosystem X written in another language Y are always a red flag. They had to reinvent a bunch of wheels, such as parsing metadata, and they probably did it badly.

See also: uv.

seabrookmx · 2h ago
Except uv is by far the best UX for Python package management out there. There's a reason they chose Rust to write this tool.

The same goes for typing.. mypy (written in Python, and contributed to by Guido himself) performed so poorly that they had to invent a bespoke compiler for it (mypyc). The other options written in Rust or node are much more performant.

Another example: the golang port of the Typescript compiler.

I agree with the take it's odd to write a nuget server in node, but the comparison to uv isn't fair. There's concrete reasons to choose a more performant language for the task.

loic-sharma · 3h ago
FWIW, the NuGet package format and the v3 server protocol are fairly simple and well documented.
oaiey · 2h ago
And so unnecessary. .NET is perfectly fine for that.
kid64 · 4h ago
Because that's how Claude decided to handle it.
mandeepj · 5h ago
> Package importer: Included package importer from existing NuGet server

Any idea how much hard drive storage space would be needed?

wvbdmp · 4h ago
https://x.com/davidfowl/status/849502394237038592

Mine is 15 gig, but I imagine 90% of it is outdated versions.

edit: removed all but the latest version of each package, now it’s 3.3 GB. The biggest non-Microsoft package for me is documentformat.openxml…

loic-sharma · 4h ago
If you import all packages on nuget.org? You’re likely looking at terabytes of data.

The import tooling can be used to migrate off another NuGet server implementation.

lfpeb8b45ez · 3h ago
*modernized