cypress

What is Cypress?

The Cypress images package the Cypress test runner — and, in the cypress/included and cypress/browsers variants, the browsers and system dependencies it needs — so you can run end-to-end and component tests for web applications in a container. Cypress is a JavaScript-based testing framework that runs tests directly in the browser, with automatic waiting, time-travel debugging, network stubbing, and video and screenshot capture on failure. The images are most often used as a job or step in CI/CD pipelines, running cypress run against a deployed or locally started application, and they remove the need to install Node.js, Cypress, and browser dependencies on every runner. They are used by QA and frontend teams that automate regression testing, and by platform teams that want a reproducible, version-pinned test environment across pipelines.

What is Echo's Cypress image?

Echo's Cypress image is a hardened build of Cypress 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 Cypress configuration, spec files, browser selection, and CI pipeline steps. 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 Cypress deployments, the distroless variant keeps all runtime operations — test execution, browser automation, and screenshot and video capture — fully intact while minimizing exposure; the default variant suits QA and platform teams that need shell access for debugging failing specs, inspecting browser behavior, or installing extra test dependencies.

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

Public Cypress images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a test runner environment used in production. Cypress images run inside CI pipelines and operational jobs with access to test credentials, application tokens, and pre-release builds of your web applications. OS-level CVEs in the base image — particularly in libraries such as openssl, libnss3, libx11, and the system libraries bundled with the browsers — 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 Cypress needs for test execution, browser automation, and screenshot and video capture while removing the packages that don't belong in a production Cypress test runner environment. 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 Cypress image with Echo's Cypress image?

Yes. Echo's Cypress image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Cypress configuration, spec files, plugins, browser selection, and recorded artifacts all continue to work without changes to your test code or CI pipeline definitions.

Is Echo's Cypress 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 Cypress workloads inside FedRAMP boundaries, where a test runner environment that drives real browsers against your applications and downloads dependencies must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Cypress image.

What is Echo's vulnerability management SLA on the Cypress 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 test credentials, application tokens, and pre-release builds of your web applications.

Is Echo's Cypress 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 Cypress deployments, the distroless variant is the leaner, more secure choice; for QA and platform teams that need shell access for debugging failing specs, inspecting browser behavior, or installing extra test dependencies, the default variant is the right fit.

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

Echo's Cypress image is built from source with only the absolute essentials needed to run the Cypress test runner environment, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Cypress 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 Cypress 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 QA and platform teams running Cypress under an ATO — whether that's automated regression testing for a citizen-facing portal or release-gating tests for an internal system — Echo's hardened Cypress image keeps the test runner environment layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍