buildpacks

What is Buildpacks?

The Buildpacks image packages Cloud Native Buildpacks tooling — the pack CLI and the lifecycle that runs detect, build, and export phases — so teams can turn application source code into runnable OCI images without writing a Dockerfile. Cloud Native Buildpacks, a CNCF project, inspect your source, select the right language buildpacks, and assemble layered images on a builder and run image, with built-in support for rebasing images when the base layer is patched. The image is used inside CI pipelines and platform build services such as Tekton, GitLab CI, and kpack, by developer platform teams that want a consistent, secure path from source to image across many applications.

What is Echo's Buildpacks image?

Echo's Buildpacks image is a hardened build of Buildpacks 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 builder and run image selection, buildpack configuration, project descriptors, and registry authentication. 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 Buildpacks deployments, the distroless variant keeps all runtime operations — source detection, buildpack execution, layer creation, image export, and rebase operations — fully intact while minimizing exposure; the default variant suits developer platform and DevOps teams that need shell access for debugging builds, inspecting builder metadata, or diagnosing registry authentication.

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

Public Buildpacks images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a build tooling image used in production. Buildpacks images run inside CI pipelines and operational jobs with access to application source code, registry credentials, and access to the container runtime. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, git, and the Go runtime dependencies — 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 Buildpacks needs for source detection, buildpack execution, layer creation, image export, and rebase operations while removing the packages that don't belong in a production Buildpacks build 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 Buildpacks image with Echo's Buildpacks image?

Yes. Echo's Buildpacks image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. project.toml descriptors, builder and run image references, buildpack lists, registry login, and CI pipeline steps all continue to work without changes to your build configuration.

Is Echo's Buildpacks 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 Buildpacks workloads inside FedRAMP boundaries, where a build tooling image that builds application images from source and pushes them to registries must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Buildpacks image.

What is Echo's vulnerability management SLA on the Buildpacks 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 application source code, registry credentials, and access to the container runtime.

Is Echo's Buildpacks 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 Buildpacks deployments, the distroless variant is the leaner, more secure choice; for developer platform and DevOps teams that need shell access for debugging builds, inspecting builder metadata, or diagnosing registry authentication, the default variant is the right fit.

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

Echo's Buildpacks image is built from source with only the absolute essentials needed to run the Buildpacks build tooling image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Buildpacks 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 Buildpacks 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 developer platform and DevOps teams running Buildpacks under an ATO — whether that's a source-to-image build service, an application build pipeline, or a rebase workflow patching run images — Echo's hardened Buildpacks image keeps the build tooling image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍