# wiremock/WireMock.Net

WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on WireMock Java, but extended and different functionality. Full documentation can be found at https://wiremock.org/dotnet/.

Repository: https://github.com/wiremock/WireMock.Net
Canonical: https://ross.abutalabs.com/products/wiremocknet
Language: C#
License: Apache-2.0
License Family: permissive
Topics: wiremock, mock-server, http-listener, tdd, testing, mocking, mockwebserver, csharp, dotnet, http, request, response, docker, azure, aspire-hosting
Last push: 2026-08-20T15:31:24+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 98, release rhythm 86, longevity 100
- inputs: {"age_days": 3515, "days_push": 13, "days_rel": 18, "gap_med": 5, "n_releases_24m": 70}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1680, forks 241 (observed 2026-08-28T04:05:21.531099+00:00)

## What it is
WireMock.Net is a flexible .NET library for stubbing and mocking HTTP responses with advanced request matching and response templating, based on the Java WireMock project. It can be embedded in unit/integration tests or run standalone as a process, Windows service, Azure/IIS host, or Docker container.

## Use cases
- mock external HTTP APIs in .NET unit tests
- stub REST endpoints with URL, header, cookie and body matching
- record and replay HTTP traffic via proxying
- simulate stateful API behavior in integration tests
- mock gRPC and GraphQL services
- run a standalone mock server in Docker for CI/CD
- template dynamic responses with Handlebars
- inject faults for chaos engineering tests

## When to choose
- you're building .NET/C# applications and need HTTP mocking in tests
- you want a WireMock-compatible mock server on the .NET platform
- you need advanced request matching, response templating, or proxy record/playback
- you need gRPC, GraphQL, or OpenAPI-aware mocking

## When to avoid
- you're not on the .NET platform (use the original Java WireMock or a language-native alternative)
- you only need simple HTTP fakes without matching or templating features
- you need mocking for non-HTTP protocols

## Facets
- artifact type: library
- maturity: active
- function: mocking, testing, http-server, e2e-testing
- domain: testing, developer-tools, apis, web-development
- platform: dotnet, cross-platform, cli, cloud
- tags: wiremock, mock-server, http-stubbing, request-matching, response-templating, grpc, graphql, openapi, record-playback, tdd, integration-testing, docker

## Member repositories
- wiremock/WireMock.Net (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:21.531099+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:41:30.058862+00:00, confidence not recorded.
  - readme: https://github.com/wiremock/WireMock.Net (fetched 2026-08-28T04:05:21.531099+00:00, sha c88ea9ec8198)
- Data as of 2026-08-30T08:39:29.467469+00:00.