Minimus has opened its entire catalog of distroless container images to the public at no cost, broadening access to a library the company says reduces application security vulnerabilities by more than 95 percent compared to conventional base images.

The company, which launched at RSAC in April 2025, builds images that strip everything except the runtime dependencies an application strictly requires — no shell, no package manager, no auxiliary tooling that widens the attack surface. That approach, broadly described as distroless, has been available in various forms for years, but Minimus positions its offering as a production-grade, maintained catalog rather than a DIY starting point.

The Market Context

The timing is not incidental. The container image supply chain has been in visible flux for the past twelve months.

Broadcom announced, effective September 29, 2025, that most Bitnami container image tags and their associated Helm charts would move to a paid model — a significant disruption for teams that had built pipelines around Bitnami's wide catalogue of application images. MinIO followed in October 2025 by announcing it would stop publishing free images to Docker Hub. And Docker itself entered the space more directly: on December 17, 2025, Docker made its Hardened Images available under the Apache 2.0 license, positioning them as a free, security-hardened alternative at the base-image layer.

The net effect across those moves is that platform and infrastructure teams can no longer treat a broad library of free, well-maintained container images as a given. Minimus is entering that gap.

What Minimus Actually Delivers

The core claim — vulnerability reduction above 95 percent — follows from the math of attack surface. A standard Debian- or Ubuntu-derived image ships hundreds of packages, the majority of which a given application never touches. Each of those packages carries its own CVE history and update cadence. A distroless image built around only the target runtime eliminates most of that exposure by construction, not by patching.

Minimus extends the model to virtual machines as well, not just containers, which matters for teams running workloads where container runtimes themselves are not available or not permitted.

The catalog opening means that images previously behind a paywall or restricted access are now freely available — covering a range of language runtimes and application stacks.

Worth flagging: the 95-percent-plus vulnerability reduction figure comes from Minimus's own materials. Independent, third-party benchmarking against a standardised image corpus would give procurement and security teams firmer ground to stand on. That said, the directional logic is sound and consistent with what comparable distroless projects have demonstrated over time.

Why This Matters for Security and Platform Teams

For a security engineer managing a large container fleet, the relevant number is not the absolute CVE count on any single image — it is the aggregate scanning and triage burden across thousands of images in CI/CD. Fewer packages per image means fewer scanner hits, faster triage, and a smaller set of genuine findings that actually require remediation. At scale, that compounds quickly.

Platform teams have a different calculus. A free, publicly available catalog only has value if it is kept current. Images that lag upstream releases become a liability; a known-good image from six months ago may be a known-vulnerable image today. How Minimus handles release cadence, EOL policy, and upstream sync will determine whether this catalog holds up in production environments — questions the company will need to answer with a track record rather than with documentation alone.

The broader picture is that the distroless and minimal-image space is now genuinely competitive. Docker Hardened Images, Chainguard's portfolio, and now a fully open Minimus catalog give platform teams real alternatives to the general-purpose images that dominated the ecosystem for the first decade of container adoption. That competition tends to raise the baseline — and for an industry that spent years treating base image provenance as a secondary concern, a higher baseline is the right direction.