go-logr/logr
A simple logging interface for Go observed · 2026-08-28
Health v2 · maintenance only
85/100
- Activity 98
- Release rhythm 61
- 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: 418
- age_days: 3515
- days_rel: 44
- days_push: 16
- n_releases_24m: 2
Adoption not part of the score
1401 stars · 87 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
logr is a minimal logging interface for Go that decouples applications and libraries from specific logging implementations. Libraries emit logs via a small Logger API while logging frameworks implement the LogSink interface to provide actual output.
Use cases
- decouple Go libraries from specific logging frameworks
- swap logging implementations without changing library code
- emit structured logs from Go applications
- pass a logger into libraries with minimal dependency fan-out
- implement a custom logging backend for Go apps
When to choose
- you write Go libraries that need logging without hard dependencies
- you want applications to control the logging implementation in main()
- you need a lightweight, structured logging API
When to avoid
- you need a full logging implementation with output handling out of the box
- you prefer the standard library log/slog directly
- your project is not written in Go
Facets
library · maturity stable
logging developer-tools backend go cross-platform logging-api decoupled-logging log-sink go-libraries
1 source
- readme: https://github.com/go-logr/logr · fetched 2026-08-28 · 69789b42df2e
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| go-logr/logr | main | 85 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem