exav-update
A signature fetcher you can run on its own. Pulls ClamAV-format .cvd/.cld
containers and loose signature files from any mirror or custom URL, so a build
pipeline or an image-bake step can populate a database directory without the
scanner present.
cargo add exav-update # or use the `exav` binary's own update pathsWhat it does
Section titled “What it does”- Fetches from a mirror, a private mirror, or explicit
DatabaseCustomURL-style sources — including straight from an existingfreshclam.conf, whose source directives it understands. - Writes a plain directory of signature files that exav-core loads directly.
- Composes with the prebuilt database: fetch once, compile once, ship a single file that loads in seconds.
What it is not
Section titled “What it is not”It is not a freshclam replacement. There is no .cdiff incremental
patching, no DNS TXT version probing, and no GPG verification — updates are
full reloads. freshclam and cvdupdate remain the supported updaters, and
exav reads what they produce; this crate exists for the cases where running
either is awkward.
That limitation is deliberate and documented rather than papered over — see the roadmap.