Anchore, Archipelo, Chainguard and Minimus

About Archipelo

Archipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage. Archipelo builds Salmon for autonomous multi-actor software systems. Archipelo, Inc. is the company developing and stewarding Salmon.^[1][3][4][5]

Archipelo states that autonomous agents, tools, runtimes, and controllers increasingly perform consequential actions themselves. Archipelo states that the resulting state alone cannot show which execution occurred, in what order, or how each state transition derived from the ones before it. Archipelo develops infrastructure that makes autonomous multi-actor software execution independently verifiable. Archipelo states that safe and reliable agents need verifiable evidence of their execution history.^[4][5]

Archipelo points to Git as showing the value of persistent, linked source code history. Archipelo says Execution Verification Infrastructure addresses a different problem, which is establishing a verifiable record of state transitions and the resulting state.

Archipelo describes execution as represented by a cryptographically signed event with explicit context. Archipelo states that Salmon captures execution as it occurs upstream within supported environments, not downstream after the event has already taken place. Archipelo states that Salmon does not visually or structurally manufacture execution continuity when execution continuity has not been established.

Archipelo states that agent generated changes can involve delegated execution, tools, subprocesses and multiple state transitions. Archipelo states that execution history provides a durable record of supported execution relationships to verify outcomes. Archipelo states that during incident investigation, teams need to work backward from a consequential state change toward the execution associated with it, to determine what caused the outcome.

One principle is that downstream systems should not be forced to establish execution history solely through retrospective inference where it can be captured during supported execution. Archipelo states that what an actor was permitted or instructed to do is distinct from what it actually executed. Archipelo states that machine-speed software systems require execution evidence that other software systems can consume and verify. Archipelo describes identity, policy, observability, security, engineering, and governance systems as solving adjacent problems.^[5]

Archipelo describes itself as a deep tech company building foundational infrastructure for verifiable autonomous systems.^[1][3][4][5]

About Chainguard

Chainguard sells hardened open source artifacts that replace vulnerable or malicious versions found publicly. Chainguard says it aims to eliminate malware and vulnerability risk across containers, dependencies, CI/CD actions and AI agent skills. Chainguard hardens open source before developers start writing a single line of code.^[1][10]

Chainguard offers container images for over 3,000 projects, and hundreds of Helm charts, rebuilt continuously by AI reconciler agents in a SLSA Level 3 environment. Every Chainguard image ships with Sigstore signatures, a signed SBOM and SLSA L2 provenance. Chainguard Factory tracks upstream changes, triggers clean rebuilds and publishes new images with updated SBOMs and provenance. Custom Assembly configures Chainguard Factory to build images to a customer's specifications, using 30,000+ packages. Chainguard gives direct access to the APKs underpinning entitled Chainguard Containers. Chainguard offers updated EOL images with low-to-zero CVEs for up to 6 months to help teams transition off legacy software. Chainguard extends its secure-by-default standard to commercial ISV software.^[1][10]

Chainguard offers over 1,200 FIPS-validated container variants and OS-level STIG hardening for regulated environments. Chainguard says zero-CVE images, signed SBOMs and full provenance simplify compliance across frameworks like FedRAMP, PCI DSS, SOC 2, CMMC and CRA. Chainguard says PCI DSS vulnerability management requirements create significant overhead for vendors handling cardholder data. Chainguard says Shift5 saved 2.5 months of engineering time per person on CVE remediation. Chainguard says Canva dodged hundreds of thousands of malware attacks on npm and PyPI. Chainguard says the Army Software Factory freed up 40% of developer time for mission-enabling innovation.^[10][11][13]

Chainguard Libraries is a malware-free catalog of open source dependencies. Chainguard offers a catalog of Python, Java, JavaScript, Go and .NET packages so teams can turn off live access to public registries. Chainguard says customers switch standard registry endpoints to Chainguard to prevent malware and shrink the CVE backlog. Chainguard Libraries works with existing artifact managers and workflows. Chainguard says every Chainguard-built version comes with full provenance and signed SBOMs. Chainguard says every remediated package includes embedded SLSA L3 provenance and SBOMs. Chainguard says every package is scanned for malicious behavior before distribution. Chainguard Repository provides every package needed on day one and lets customers configure cooldowns.^[12]

Chainguard VMs are minimal Linux images based on Chainguard OS and come in three types. Chainguard VMs include only the essential components for running containers: a Linux kernel, systemd, glibc, and optional userspace tools like SSH. Chainguard VMs support AWS, Azure, Google Cloud and on-premise hypervisors including VMware, Nutanix and OpenStack. Chainguard VMs carry a CVE remediation SLA of 7 days for critical and 14 days for high, medium, and low through automated rebuilds. Chainguard VMs support kernel-independent FIPS 140-3-validated cryptography. Chainguard VMs offer DISA STIG hardening and CIS Benchmark Level 1 hardening.^[13]

Chainguard offers 30,000+ zero-CVE packages, including every package powering Chainguard Containers. Chainguard says secure packages can be swapped in whether a team builds with Bazel, Melange, Dockerfiles or another tool. Chainguard says every artifact ships with build-time generated SBOMs. Chainguard OS Packages has a FIPS variant built with the latest versions of Chainguard's FIPS-validated cryptographic modules. Chainguard offers a catalog of 1,000+ hardened third-party actions. Chainguard Actions are drop-in replacements for upstream GitHub Actions. Chainguard re-verifies and rehardens every action whenever its upstream version changes or a new attack pattern emerges. Every Chainguard Action ships with a full hardening report. Chainguard Guardener analyzes and rebuilds Dockerfiles layer by layer, maps packages and tests incrementally. Guardener opens a migration pull request for all actions with a drop-in Chainguard equivalent. Chainguard offers 1,000+ hardened community skills that are safe from malicious instructions.^{[10][14][15][16]}

Chainguard says reconciler bots and AI agents run continuously across its entire catalog. Chainguard says every package is rebuilt from source in an isolated SLSA L3 environment on its own minimal OS. Chainguard says every build starts with an immutable SHA reference to the upstream source. Chainguard says it signs every artifact it ships. Chainguard says every image is rebuilt with a separate apko toolchain to produce a bitwise-equivalent result.^[1][17]

Chainguard Checks runs CI inside Chainguard microVMs that produce cryptographically signed attestations. Chainguard Checks is currently in beta and is a Technology Preview. Chainguard Workspaces isolates untrusted code inside Chainguard-hardened microVMs. Chainguard Workspaces is currently in beta and is a Technology Preview. Chainguard Harness builds an application from source in an isolated environment and lets Mythos 5.1 hunt through a live instance for exploitable vulnerabilities. Chainguard Harness is currently in beta and is a Technology Preview.^{[1][4][6][18][19][20]}

About Minimus

Minimus sells minimal container images that it rebuilds from upstream source, with only the packages needed to run the application. Minimus is winding down operations, and Echo has acquired key Minimus technology and assets. Minimus says it is working with the Echo team and meeting with every Minimus customer to provide support during the transition period.

Minimus images contain only the software needed to run the application. Minimus images have shells, package managers, and network utilities stripped out. Minimus builds its images from source continuously, and the images are OCI-compliant, with FIPS 140-3 modules available. Minimus compiles each application in a SLSA 3 build environment from upstream project source code and includes only the libraries the application needs to run. Minimus monitors tens of thousands of open source projects and rebuilds images in a SLSA Level 3 pipeline when updates occur. Minimus provides images for LLM, app development, and cloud native infrastructure.^[5][6]

Minimus gives a contractual guarantee of zero known CVEs at delivery, with a 48-hour remediation SLA for newly disclosed vulnerabilities. Minimus patches critical CVEs within 48 hours of upstream availability, and high and medium CVEs within 14 days. Minimus sets a 24 hour SLA for critical and high CVEs on KEV, and 48 hours for all other critical and high CVEs. Minimus offers FIPS 140-3, STIG, NIST and CIS ready images for sensitive workloads. Minimus images come with automated testing and documented results per build, and support FedRAMP, DORA, and NIS2 posture requirements. Minimus is both SOC-2 and ISO 27001 certified, and Minimus makes the reports available by request.^[5][6][7]

Minimus lets customers configure their own hardened container images, and Minimus takes care of the updates and maintenance. Customers can build atop the thousands of secure base images from Minimus. Minimus draws real-time threat intelligence from EPSS, CISA-KEV, and Minimus Labs to prioritize upstream vulnerabilities by actual likelihood of exploit.^[5][6]

Minimus offers Actions to integrate with tooling such as GitHub, Slack, and webhooks. Minimus automatically triggers events in Slack, Jira, GitHub, and more. Minimus connects to development, chat, and ticketing tools and to the rest of a security stack. Minimus provides skills and config tools for Claude, Codex, Cursor, and more to migrate to and build on Minimus images.^[5][6]

Minimus offers a SaaS management console, and images can be pulled from the Minimus registry or from whatever registry a customer uses, including air gapped ones. Minimus supports pulling from the registry of your choice, with fully air-gapped support available, and Minimus publishes Hardened Helm Charts versioned by Minimus. Minimus can sync images to the registries a customer already uses, even air-gapped ones. Minimus images are API-compatible with what customers already run, and the change is an update to the Dockerfile followed by a rebuild.^[5][6]

Minimus offers open access to hardened images for everyone, with an upgrade for private builds, SLA-backed support, and the controls enterprise teams need. Minimus offers 1,000s of near 0 CVE images built from source. Minimus is built for the needs of enterprise security teams and fast moving developers. Global financial institutions and startups are named as customers of Minimus. The Minimus founders created Twistlock, which Palo Alto Networks acquired, and authored NIST SP 800-190, the federal standard for container security. Minimus has a global team that provides round-the-clock support, 365 days of the year.^[5][6][7]