• Skip to main content
  • Skip to secondary menu
  • Skip to footer

Market Analysis

Connecting the Dots, Quantifying Technology Trends & Measuring Disruption

  • AI Market Analyzer
  • Tech News
    • Project Dashboard
  • Domain Marketplace
  • Sponsored Post
  • About
  • Contact

RMQA Opens Every Archive in a Software Release and Checks What Is Really Inside Before You Publish

November 4, 2026

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.

Filed Under: Projects Tagged With: cybersecurity, enterprise software, startups and funding

Footer

Recent Posts

  • China Turns AI Model Distillation Into Industrial Policy and Weakens the Reach of US Chip Controls
  • AI-Found Software Flaws and the Rush to Patch Them Are Now a Market Risk After a Week of US Outages
  • Ohio Voters Put $17 Billion of Amazon Data Center Spending at Risk as Local Bans Spread
  • US Remote Access Chip Rule and FCC Optics Ban Squeeze Southeast Asia Data Centers and Nvidia China Exposure
  • Microsoft Puts Word, Excel and PowerPoint Inside Copilot and Turns Office Into an AI Front Door
  • OpenAI Cuts GPT-6.2 Astra Prices 20% as Microsoft MAI Code 2 Undercuts Frontier Coding Models
  • Tencent Q3 Shows New AI Products Cost About RMB15 Billion in Operating Profit as Capex Hits 39% of Revenue
  • Anthropic IPO Heads for the Top of Its Range as $900 Billion in Compute Commitments Go Public
  • Nvidia Q3 Revenue Hits $115.8 Billion but the Q4 Margin Guide Drops Three Points as the Board Rules Out Jensen Huang
  • Emboldened Iran and a Weakened Trump Leave US Stocks, Bonds and Oil Pricing a Peace That Has Not Arrived

RSS feed: Market Research Media Market Research Media

  • Four Vendor Surveys on Missed AI Returns Each Find the Problem Their Sponsor Sells a Fix For
  • Wasabi Study Puts Unplanned Infrastructure Spending at $63.4 Billion, With Germany Overspending by 7.1 Billion Euros
  • CSC Survey Finds 88% of Private Capital GPs Spend Up to Half Their Finance Time Checking Administrator Work
  • Lenovo Survey Finds 80% of IT Leaders Tie AI Success to the Digital Workplace and Only 10% Have Redesigned It
  • Claude and ChatGPT Integrations Killed the Headless CMS Market
  • Survey Margin of Error Explained, What Plus or Minus 3 Points Covers and What It Leaves Out
  • Morgan Stanley Pulse Survey Finds Bearish Investor Sentiment Rising to 42 Percent as Inflation Fears Grow
  • A Stronger Week Across the Network, October 4–10, 2026
  • The Tariff Map Is Becoming an Industrial Policy Map—and the U.S. Economy Is Paying the Price
  • PC Shipments Fall 22.4% as Higher Component Costs Price Buyers Out

Media Partners

  • Analysis
  • Technology Conferences
  • OSINT
  • Defense Market
  • Cybersecurity Market
  • Event Calendar
  • Calendarial
  • Opinion
  • 3V
  • Media Presser
  • Exclusive Domains

Copyright © 2026 MarketAnalysis.com | Terms of Service | Privacy Policy | Supplier Disclaimer | The Website Coded and Designed by SoftDev Studio

Media Partners: Technologies | Photography | Referently

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Do not sell my personal information.
Cookie SettingsAccept
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
SAVE & ACCEPT