nordisk/holger

holger-znippy-composer-repository — crate card

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

• One-line pitch: znippy-archive-backed Composer (PHP / Packagist) repository implementing the Composer v2 metadata protocol.
• Does: ComposerRepoZnippy implements RepositoryBackendTrait serving packages.json (repo root pointing at p2), p2/{vendor}/{package}.json (per-package version metadata) and dist/{vendor}/{package}/{ref}.zip (distributable zip). Metadata stored in the archive as p2/{vendor}/{package}.json, dists as dist/{vendor}/{package}/{ref}.zip. Generic reader-backed (with_archive/with_reader).
• 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-composer. "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: