Build pipelines check that the code compiles and the tests pass. Almost nothing checks the finished release as a whole. So things like this reach users: an arm64 archive with the amd64 program inside, a download still holding last week’s build, a macOS file that was never uploaded, a checksums file made before an archive was rebuilt, a licence missing from the Windows zip. Every step went green.
rmqa, short for release manifest QA, checks the release itself. You write a manifest once that describes what every release must contain. rmqa opens the real archives and programs and reports, file by file, what’s missing or wrong. It runs after the build and before the publish step, on your machine or as a CI gate.
The Pitch in Four Numbers
- 24 of 24 kinds of broken release caught in the tests, each with the right finding code.
- 0 errors on a real release, ukue 0.1.0, checked straight from its GitHub downloads.
- 1 binary, standard library only, for Linux, macOS and Windows, with nothing else to install.
- 15 seconds, the time limit when rmqa runs a program to check its version, in an empty temporary folder.
How It Works
The manifest is a short TOML file listing the platforms and what each download has to contain. rmqa init writes one for you from a release you know is good. After that, every release is checked against it.
rmqa reads the archives with its own readers: tar.gz, tgz, tar.bz2, tar.xz, tar.zst, tar, zip, gz, xz and zst. It recognises programs by their headers, ELF for Linux and the BSDs, Mach-O for macOS including universal binaries, and PE for Windows. So it knows when a download labelled arm64 actually holds an amd64 build.
It checks that every expected download is there, that the right program for the platform is inside each archive, that the version string in the program is the one you’re releasing, that licences are included and that checksums match. It verifies minisign and key-based cosign signatures against a public key you supply, and can require a signature on every file. If the manifest says run = ["--version"], it runs programs built for the machine it’s on, with a 15-second limit, and checks the others by header and version string.
It exits 0 when the release is ready and 1 when it isn’t. Output comes as GitHub Actions annotations, JSON or Markdown, and there’s a ready-made GitHub Action. Every rmqa release is checked by rmqa before it goes out. The first test run caught a bug in rmqa itself.
What It Catches
The project’s posts walk through the real cases: checking a draft GitHub release before anyone can download it, a Rust-style set of targets with the Intel Mac build missing, env files and private keys that slipped into release archives, and the classic “permission denied” after unzipping because the executable bit got lost. It also keeps a machine-readable record of what every release shipped.
Who It’s For
- Maintainers who publish releases on GitHub, including draft releases.
- Teams using GoReleaser or Rust’s cargo-dist, who build for many platforms at once.
- Any project shipping compiled programs in Go, Rust, C or C++, Zig, Swift or native .NET. rmqa looks at the files, not at how they were built.
- Companies that can’t afford a broken release reaching customers, especially for paid software.
Limits
rmqa can’t open .deb, .rpm, .msi or .dmg files yet. Those are checked for presence, size and checksum only. It doesn’t verify keyless Sigstore or GPG signatures, and it doesn’t check container images or package registries. It isn’t a replacement for signing, SBOM or provenance tools. Those tell you who made a file and what’s in it. rmqa tells you the files you’re about to publish are the right ones, complete, for the right platforms, with the right version inside.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
rmqa is free under Apache 2.0, with no paid tier. Release quality is part of software supply-chain security, which companies already pay for. The paid paths are support for the formats it can’t open yet, .deb, .rpm, .msi and .dmg, plus container images; a hosted check that runs on every release and keeps a signed record; and enterprise features like policy across many repositories. Vendors who ship desktop or on-premises software, where a broken download means support tickets and refunds, are the obvious first buyers.
2. What real problem does it solve?
The gap between a green pipeline and a correct release. Every build step can pass while the thing you publish is still wrong. Users find out first, and they find out by downloading something that doesn’t run.
3. The technology in plain words
Think of the last check at a warehouse before a delivery van leaves. Someone opens every box, checks that the item inside matches the label, that the manual is in there and that the serial number is right. rmqa does that for software, box by box, before the van goes.
4. Moat and differentiation
Release tools build and publish. Signing and SBOM tools describe. rmqa is the one that opens the box and checks. It’s small, has no dependencies and is honest about what it doesn’t cover. The moat that can grow is format coverage and the catalogue of real release mistakes it knows how to spot, along with a place in CI pipelines, which is sticky once it’s there.
Why It Matters
Release mistakes are embarrassing, costly and sometimes dangerous, like a private key shipped inside an archive. They’re also easy to catch if anything looks. A small check that runs before the publish step is cheap insurance for every project that ships binaries.
Follow the Project
Start with the quick start, read why a green CI run isn’t enough, see how it was tested with 24 broken releases, or get the code from the rmqa repository on GitHub. rmqa is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.