holger-nexus-connector — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: Agent connector for Sonatype Nexus — a
ConnectorTraitimpl over the Nexus REST API. - Does: Implements
ConnectorTrait(list_repositories / list_assets / download_asset / upload_asset) against Nexus. Auth viaConnectorAuth(None / Basic / OidcToken withfetch_oidc_token/ Mtls). Bounds memory against malicious upstreams:read_cappedenforces caps on bodies (MAX_DOWNLOAD_BYTES = 8 GiB,MAX_JSON_BYTES = 256 MiB) via Content-Length and while streaming. - Key deps:
traits,async-trait,reqwest(rustls-tls, json),serde/serde_json. - Shape: lib, single
lib.rs. - Observed role in the workspace: One of the three source/target connectors re-exported by
holger-agent-lib; also used as a dev-dep in agent-cli integration tests. ItsConnectorAuth/fetch_oidc_tokenare the workspace's shared auth types.
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: