nordisk/holger

holger-znippy-go-repository — crate card

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

• One-line pitch: znippy-archive-backed Go module proxy implementing the GOPROXY protocol.
• Does: GoRepoZnippy implements RepositoryBackendTrait serving @v/list (versions), @v/{ver}.info ({Version, Time}), @v/{ver}.mod (the go.mod) and @v/{ver}.zip (module zip). Files stored in the archive as {module}/@v/{ver}.{info,mod,zip}, matching the on-disk module-proxy cache layout. Uses a generic ZnippyReader (with_archive/with_reader constructors).
• 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-go. "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: