microsoft/go-winio
Win32 IO-related utilities for Go observed · 2026-09-01
Health v2 · maintenance only
68/100
- Activity 100
- Release rhythm 8
- Longevity 100
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: n/a
- age_days: 3868
- days_rel: n/a
- days_push: 3
- n_releases_24m: 0
Adoption not part of the score
1075 stars · 216 forks observed · 2026-09-01
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Go library from Microsoft providing Win32 IO utilities, focused on named pipes and file handles, including using named pipes as a net transport. It uses IO completion ports for non-blocking IO on Windows Vista and newer.
Use cases
- use named pipes as a network transport in Go on Windows
- perform non-blocking Win32 file IO from Go
- communicate with Windows services over named pipes
- build Windows container tooling that talks to named pipes
- access low-level file handles efficiently in Go
When to choose
- you need named pipe or Win32 handle IO in a Go program on Windows
- you want non-blocking IO that integrates with Go's goroutine scheduler
- you're building Windows-specific infrastructure like Docker/container components
When to avoid
- your application is cross-platform and doesn't need Windows-specific IO
- you only need standard network sockets or regular file IO
- you need to support Windows versions older than Vista
Facets
library · maturity stable
file-system networking concurrency developer-tools windows operating-systems windows go named-pipes win32 io-completion-ports go-library
1 source
- readme: https://github.com/microsoft/go-winio · fetched 2026-09-01 · 10a9fedf331f
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| microsoft/go-winio | main | 68 |
For agents
markdown · JSON · MCP: product_card(name="microsoft/go-winio")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem