Minimus
August 16, 2026 commercialThe section your link pointed to isn't on Minimus's page any more, so we've brought you to the top.
Summary
Minimus is a commercial container-security platform that provides hardened, minimized base images with close to zero known CVEs, available free through its Community Edition with unauthenticated pulls from the full image catalog, while an Enterprise Edition adds private image management and supply-chain protection. Images are consumed by pulling them into existing Docker or Kubernetes workflows, much like pulling from any registry, and each is built from source, scanned continuously, signed with SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue., and offered in both a full production variant and a shell-less, non-root distroless variant. It targets platform and security teams looking to replace Alpine, Debian, or Ubuntu bases, including those needing FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto., NIST, or STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against. compliance for regulated environments like FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one.. Its documentation positions it as a distroless alternative for teams migrating off traditional Linux base images.
How Minimus helps
Which base images in my stack are dragging in the most CVEs?
swaps them for hardened, minimal builds maintained and rescanned daily, so the vulnerability count a team has to track drops at the source instead of after a scan
Which CVEs in a given image actually trace back to the package I depend on versus something bundled underneath it?
the advisories view separates origin package from affected package and shows a per-CVE breakdown of what within that origin package is affected
Can I trust that a pulled image hasn't been tampered with before it reaches a cluster?
every image is signed with an SBOM and built through a documented pipeline, so signatures can be verified with standard tooling before deployment
Did an automated remediation rule actually fire when it was supposed to?
each action rule shows a status indicator for its last run and a running trigger count, so a silent failure is visible without digging through logs
Can I prove to an auditor what remediation actions ran and when?
every invocation, success or failure, is written to an activity log with a link back to the rule that fired it, giving a durable record for review
Do my images meet FIPS or NIST compliance requirements without extra rework?
images are offered as FIPS 140-3 verified builds with published CMVP certificates, covering day-one compliance needs for regulated environments
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Minimus, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Minimus puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · Minimus vendor page4 readings of Minimus's pricing page since Jul 2026, with 1 change to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
minimus.io, every changeMinimus's home and pricing pages and 23 more pages as they looked each month from April 2025 to October 2026: 35 renders, 3 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
23 entries
No entries match these filters.
- August 20264
- July 20264
- June 20262
- May 20262
- April 20263
- March 20264
- February 20263
- January 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.