Download
Static binaries and a scratch image.
Built and published by the release that carries the tag, each architecture compiled natively on its own runner rather than emulated. Check the sum before you run it.
v0.3.0
scratch, no shellVerify it
Two commands, and they matter more here than for most software: this binary is going to be the thing that reads your mail.
V=0.3.0; T=x86_64-unknown-linux-musl curl -fsSLO https://github.com/metronom72/mxhop/releases/download/v$V/mxhop-v$V-$T curl -fsSLO https://github.com/metronom72/mxhop/releases/download/v$V/SHA256SUMS-$T sha256sum -c SHA256SUMS-$T mxhop-v0.3.0-x86_64-unknown-linux-musl: OK
For the image, pin the digest rather than the tag — a tag can be moved, a digest cannot:
docker buildx imagetools inspect ghcr.io/metronom72/mxhop:0.3.0
Not yet signed. There is no Sigstore or cosign signature on these artifacts today, so the checksum proves the file is intact, not who built it. If you need provenance, build from source — the release workflow is in the repository and the build is reproducible from a tag.
Build it yourself
Stable Rust, no build scripts, no vendored C. The static target is what the releases ship:
git clone https://github.com/metronom72/mxhop
cd mxhop
rustup target add x86_64-unknown-linux-musl
cargo build --release --target x86_64-unknown-linux-musl
cargo test
The test suite includes two that are really assertions about the project rather than the code: one parses every tracing call in the source and fails if any would print a message's content, and one checks the built binary has no dynamic dependencies at all.