uber-go/zap
Zap is a high-performance, structured logging library for Go that provides type-safe APIs for logging objects and arrays. It supports integration with Go's standard log/slog interface, gRPC, and io.Writer streams, while offering comprehensive testing utilities and in-memory observers for verifying log output. The system also includes internal optimizations such as zero-allocation buffers and buffered write syncers to improve throughput.
63.6
Adequate · 1 August 2026
8.6k
lines of production code
Go
primary language
3
bus factor · 153 authors in all
3
measurements over time
How it got here
2016–2017 · Performance optimization and testing infrastructure
This period focused on enhancing logging performance through a new buffered write syncer and a zero-allocation buffer pool, alongside introducing Go generics for type-safe array logging. Significant effort was also dedicated to testing infrastructure, including an in-memory log observer, gRPC compatibility wrappers, and automated benchmarking tools to measure and compare structured logging performance.
12 changes
2019–2023 · Go 1.21+ integration and internal refactoring
This period focused on integrating Go 1.21's log/slog via the new zapslog package and adding a streaming io.Writer for flexible log output. Internal refactoring included a leveled enabler to break cyclic dependencies, a generic object pool, and an efficient stack trace capture utility. The work also involved updating dependencies and adding integration tests for gRPC.
9 changes
Survey your own repository
uber-go/zap was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 5b81b37b81 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.