connectrpc.com/connect.NewResponse
third-partyThe 1311th most-called third-party function by production calls. Called 574 times across 9 modules; 477 of those run outside tests and generated code.
4% in production calls vs 2026-W37 (457 → 477)
- prod calls
- 477
- non-test, non-generated
- all calls
- 574
- total callsites
- modules
- 9
- distinct callers
- in loop
- <1%
- of prod calls
- in tests
- 17%
- 97 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function100%A direct call to an exported package function, resolved by type.
who calls this
Notable callers
Production calls into NewResponse from notable Go projects. Open one on the map to see what else it hammers.
where it's called
Callsites in the wild
12 representative callsites of 574, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
-
connectrpc.com/connect @v1.21.0
connect_ext_test.go:2516
in loop test - in loop test
- in loop test
- in loop test
- in loop test
-
-
gitea.dev @v1.27.3
routers/api/actions/ping/ping.go:32
-
-
-
connectrpc.com/connect @v1.21.0
handler.go:133
-
top callers
The modules that reach for it
The modules that call NewResponse most in this snapshot.
- github.com/bytebase/bytebase25945%
- github.com/grafana/pyroscope17330%
- github.com/usememos/memos8916%
- connectrpc.com/connect244%
- github.com/grafana/alloy102%
siblings
More from connectrpc.com/connect
The other most-called functions in this package. See all →