microsoft/ebpf-for-windows
eBPF implementation that runs on top of Windows observed · 2026-08-28
Health v2 · maintenance only
86/100
- Activity 99
- Release rhythm 60
- Longevity 100
Flags: prerelease_only
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 35.0
- age_days: 1974
- days_rel: 14
- days_push: 7
- n_releases_24m: 11
Adoption not part of the score
3553 stars · 304 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
eBPF for Windows is an MIT-licensed implementation of the eBPF runtime that runs on top of the Windows kernel, letting developers reuse familiar Linux eBPF toolchains (clang, ELF bytecode, verifier APIs). It verifies and loads eBPF programs either as natively generated Windows driver modules or via a uBPF JIT service, enabling kernel programmability for networking, DoS protection, and observability.
Use cases
- run eBPF programs on Windows
- port Linux eBPF tools and programs to Windows
- packet filtering and network processing on Windows servers
- mitigate DDoS attacks at the kernel level on Windows
- observe and trace kernel and network events on Windows
- verify eBPF bytecode before loading it into the Windows kernel
- compile eBPF programs into signed Windows drivers
When to choose
- You need eBPF-based observability, tracing, or packet processing on Windows rather than Linux
- You want to reuse existing eBPF toolchains, bytecode, and APIs from the Linux ecosystem on Windows
- You need verified, safe kernel extensibility on Windows, especially with HVCI enforced (prefer the native driver mode)
- You are building Windows networking or security tooling that benefits from programmable kernel hooks
When to avoid
- You are targeting Linux or macOS, where the kernel's native eBPF stack is the right choice
- You require full feature parity with Linux eBPF, since this project is a work-in-progress with evolving hook and API coverage
- You need a guaranteed production-hardened eBPF stack today rather than an actively maturing one
- You only need user-space sandboxing or tracing without kernel integration
Facets
framework · maturity active
security networking tracing monitoring developer-tools operating-systems security networking developer-tools windows ebpf bpf kernel-programmability jit-compiler verifier windows-kernel observability packet-filtering ddos-protection xdp driver-development native-code-generation
1 source
- readme: https://github.com/microsoft/ebpf-for-windows · fetched 2026-08-28 · bc4f31a32aaa
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| microsoft/ebpf-for-windows | main | 86 |
For agents
markdown · JSON · MCP: product_card(name="microsoft/ebpf-for-windows")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem