// the find
go-resty/resty
Simple HTTP, REST, and SSE client library for Go
resty is Go's most popular HTTP client wrapper, sitting on top of net/http to add REST conveniences: retries, redirects, multipart, digest auth, SSE, and a curl-command dump for debugging requests. Aimed at anyone writing a Go service that talks to other HTTP APIs and doesn't want to hand-roll retry/backoff logic on every call site.
Test coverage is enforced, not just claimed — every feature file (retry.go, digest.go, sse.go, hedging.go) has a matching _test.go, backed by a 100%-patch-coverage requirement on PRs and a codecov badge that isn't just decorative. It's under active development, not coasting on past popularity — v3 is a real rewrite with its own go.dev vanity URL (resty.dev/v3) and a go1.23 floor. The curl-command generation and http-trace support are genuinely useful for debugging outbound calls in production, which most HTTP clients don't bother with.
The README has no code in it at all — every usage example lives on an external site and a separate go-resty/docs repo, so you can't evaluate the API surface without leaving GitHub. v3 folds circuit breaker, rate limiter, load balancer, and hedging into what's supposed to be a 'simple' HTTP client — that's resilience-engineering scope creep for a dependency that used to just be a REST wrapper, and it's more surface area to audit if you only wanted the request-building parts. It's a single-maintainer project (the Contribution section is written in first person singular) for a library with 11.8k stars and presumably heavy production use — that's a bus-factor risk worth knowing about before building critical-path code on it.