nordisk/holger

holger-znippy-nuget-repository — crate card

Reverse-engineered (from source — verify, don't trust the name)

• One-line pitch: znippy-archive-backed NuGet (.NET) repository implementing the NuGet V3 protocol.
• Does: NugetRepoZnippy implements RepositoryBackendTrait serving the V3 service index (/v3/index.json), flat-container version lists (/v3-flatcontainer/{id}/index.json) and packages (/v3-flatcontainer/{id}/{ver}/{id}.{ver}.nupkg), ids lowercased per convention. Packages stored in the archive as {id}/{ver}/{id}.{ver}.nupkg. The service index PackageBaseAddress @id must be an absolute externally-reachable URL (from ron_base_url) — NuGet follows it for every subsequent fetch, so a hardcoded loopback would break remote clients; defaults to dev loopback when unconfigured.
• Key deps: traits, znippy-common, anyhow.
• Shape: lib, single lib.rs. Shared znippy-backend pattern.
• Observed role in the workspace: Registered in server-lib as repository-znippy-nuget. "Real protocol" per CLAUDE.md.

Fill in (one line each — only the human knows these)

• Primary consumer(s):
• Why it exists (vs the obvious alternative):
• Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
• Release cadence & independence (rides a parent? own repo someday?):
• Status (production / prototype / experimental / stubbed):
• Must-NOT-change invariant:
• Biggest known gap or TODO:
• Anything a newcomer would get wrong about it: