composer

What is Composer?

The Composer image packages Composer, the standard dependency manager for PHP, along with a PHP CLI runtime, so you can install and autoload PHP packages in a container without installing Composer on the host. Composer reads composer.json and composer.lock to resolve dependencies from Packagist and other repositories, generates an optimized autoloader, and runs scripts as part of install and update. It is the backbone of the modern PHP ecosystem, used by frameworks and applications such as Laravel, Symfony, Drupal, and Magento. The official image is most often used as a build stage in a multi-stage Dockerfile that runs composer install --no-dev before copying the vendor directory into the final PHP image, and as a CI job image for installing dependencies and running scripts. It is used by PHP developers, build engineers, and platform teams that need a reproducible, version-pinned Composer across environments.

What is Echo's Composer image?

Echo's Composer image is a hardened build of Composer on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your composer.json and composer.lock files, autoloading, and private repository configuration. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

• Distroless variant — optimized for runtime use, with the smallest possible attack surface
• Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production Composer deployments, the distroless variant keeps all runtime operations — dependency resolution, package installation, autoload generation, and script execution — fully intact while minimizing exposure; the default variant suits PHP and platform teams that need shell access for debugging dependency conflicts, inspecting the Composer cache, or running custom scripts.

What is the difference between Echo's Composer image and the public Composer image?

Public Composer images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a dependency management tooling image used in production. Composer images run inside CI pipelines and operational jobs with access to private repository tokens, source code, and build artifacts. OS-level CVEs in the base image — particularly in libraries such as openssl, libcurl, libzip, and git used to download packages — create exploitable paths in an environment that application-level controls never see. Because tooling images are pulled and executed constantly across pipelines, they are also a steady source of scanner noise — every package in the base becomes a finding your security team must triage, even when none of it is exercised by the job. Echo's build retains everything Composer needs for dependency resolution, package installation, autoload generation, and script execution while removing the packages that don't belong in a production Composer dependency management tooling image. As we covered in our post on how to protect your company from software supply chain attacks, build and automation images that run with access to source code, credentials, and deployment targets are a high-value path into everything downstream. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my Composer image with Echo's Composer image?

Yes. Echo's Composer image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Dependency resolution, lockfile installs, private repository authentication, autoload optimization, and script hooks all continue to work without changes to your composer.json, Dockerfiles, or CI configuration.

Is Echo's Composer image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Composer workloads inside FedRAMP boundaries, where a dependency management tooling image that downloads and executes third-party packages and install scripts must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Composer image.

What is Echo's vulnerability management SLA on the Composer image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a tooling image that is pulled and run constantly across pipelines with access to private repository tokens, source code, and build artifacts.

Is Echo's Composer image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Composer deployments, the distroless variant is the leaner, more secure choice; for PHP and platform teams that need shell access for debugging dependency conflicts, inspecting the Composer cache, or running custom scripts, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Composer?

Echo's Composer image is built from source with only the absolute essentials needed to run the Composer dependency management tooling image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Composer version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's Composer image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For PHP application and platform teams running Composer under an ATO — whether that's a Laravel or Symfony application build, a CI dependency-install stage, or a multi-stage Docker build — Echo's hardened Composer image keeps the dependency management tooling image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍