Chainguard Hits 1 Billion Container Build Manifests: What the Numbers Mean for Software Supply Chain Security
The secure container specialist doubled its output in six months. What's interesting is the machinery behind the number, not the number itself.
Key points
- Chainguard reported passing 1 billion container build manifests in the last six months, up from 500 million.
- The company's catalog now holds more than 3,000 unique container images and 675,000 image versions.
- The scale increase forced a rebuild of the internal systems that produce and track secure images.
- Container build manifests are the recipes that describe how software is assembled, and they matter for tracing what is inside the code companies run.
Chainguard, a company that sells pre-hardened building blocks for cloud software, says it's crossed 1 billion container build manifests produced. Six months ago that figure sat at 500 million. The milestone was shared by the company and picked up by The Hacker News. On its face it's a vanity metric. Look closer and it's a story about what modern software supply chain security actually costs to run.
What is a build manifest, in plain English?
A build manifest is a written recipe for a piece of software: every ingredient, every version, the order they were combined. When a company runs software in the cloud, that recipe is what lets security teams answer the question of what exactly is inside the thing they're running.
Containers are the standard packaging for cloud software today. Think of a container as a sealed lunchbox holding an application and everything it needs to run. The manifest is the label on the lunchbox.
Chainguard's business is producing containers that are stripped, patched and rebuilt constantly so customers inherit fewer known flaws. Each rebuild generates a new manifest. A billion of them means a lot of rebuilding.
Why does the scale matter?
Scale matters because security only works if it keeps pace with change. A container image that was clean on Monday can contain a newly disclosed vulnerability by Friday. A slow rebuild pipeline leaves customers exposed.
The catalog covers more than 3,000 unique container images across 675,000 versions. That version count is the tell. It means the same image is being rebuilt again and again as upstream code and security fixes land.
| Metric | Six months ago | Now |
|---|---|---|
| Build manifests produced | 500 million | 1 billion+ |
| Unique container images | not disclosed | 3,000+ |
| Image versions in catalog | not disclosed | 675,000 |
Why this touches policy, not just engineering
Regulators have spent the last three years pushing companies to know what's inside their software. Executive Order 14028, signed in May 2021, directed federal agencies to require a Software Bill of Materials, a machine-readable inventory of software components, from their suppliers. We've tracked that obligation since July, most recently in our report on how CISA and allies rewrote the minimum SBOM elements for 2026. The European Union's Cyber Resilience Act entered into force in December 2024 and imposes similar ingredient-listing duties on manufacturers of products with digital elements, with main obligations applying from December 2027.
Build manifests are raw inputs that make a Software Bill of Materials possible. A supplier that can't produce a reliable manifest at speed can't produce a reliable inventory at speed either. That's the regulatory subtext under Chainguard's number. Our earlier piece on why those ingredient lists are often wrong before they're filed shows why the rebuild cadence Chainguard is describing matters to compliance teams, not just engineers.
The company hasn't published a detailed white paper on its internal system rebuild, only a summary post. Claims about throughput and provenance should be read against that caveat.
What should a buyer take from this?
Treat the figure as evidence of pipeline capacity, not a guarantee of security outcomes. A billion manifests proves the machinery works. It doesn't prove any given image is free of flaws on any given day.
Procurement teams evaluating secure-base-image vendors should ask: how quickly does a newly disclosed vulnerability move from public disclosure to patched image, whether signed provenance is produced for every build, and whether the vendor's manifests plug cleanly into the buyer's own inventory tooling. Those are the questions that turn a headline number into a purchasing decision.
