wiremock
The official WireMock image — a flexible API mocking server that simulates HTTP services for integration testing, local development, and CI environments.
What is WireMock?
The WireMock image packages WireMock, a popular open-source API mocking tool that simulates HTTP services so teams can develop and test against dependencies that are unavailable, slow, or costly to call. WireMock runs as a standalone server that loads request-matching stubs from JSON mapping files or an admin API, supports response templating, fault injection, delays, proxying, and request verification, and exposes a recorded request journal for assertions. The image listens on port 8080 and is commonly started in CI pipelines and Docker Compose or Kubernetes test environments. It is used by developers, QA, and platform teams that need reproducible service virtualization.
What is Echo's WireMock image?
Echo's WireMock image is a hardened build of WireMock 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 mappings and files directories, response templating, proxy settings, and startup flags. 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 WireMock deployments, the distroless variant keeps all runtime operations — request matching, stub responses, fault simulation, proxying, and request verification — fully intact while minimizing exposure; the default variant suits developer and QA teams that need shell access for loading mappings, inspecting the request journal, or debugging stubs.
What is the difference between Echo's WireMock image and the public WireMock image?
Public WireMock images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a API mocking server used in production. WireMock images run inside CI pipelines and operational jobs with access to stubbed API contracts, recorded request data, and sometimes proxied credentials. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the bundled JVM 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 WireMock needs for request matching, stub responses, fault simulation, proxying, and request verification while removing the packages that don't belong in a production WireMock API mocking server. 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 WireMock image with Echo's WireMock image?
Yes. Echo's WireMock image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. mapping and __files directories, admin API calls, response templating, proxy recording, and CLI flags all continue to work without changes to your tests or stub definitions.
Is Echo's WireMock 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 WireMock workloads inside FedRAMP boundaries, where a API mocking server that simulates third-party services and can proxy traffic to real systems during tests must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the WireMock image.
What is Echo's vulnerability management SLA on the WireMock 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 stubbed API contracts, recorded request data, and sometimes proxied credentials.
Is Echo's WireMock 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 WireMock deployments, the distroless variant is the leaner, more secure choice; for developer and QA teams that need shell access for loading mappings, inspecting the request journal, or debugging stubs, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in WireMock?
Echo's WireMock image is built from source with only the absolute essentials needed to run the WireMock API mocking server, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the WireMock 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 WireMock 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 and QA teams running WireMock under an ATO — whether that's integration test environments, contract testing in CI, or simulated dependencies in a staging stack — Echo's hardened WireMock image keeps the API mocking server layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)