Skip to content
callcount

google.golang.org/grpc/metadata.NewOutgoingContext

third-party

The 3117th most-called third-party function by production calls. Called 441 times across 75 modules; 191 of those run outside tests and generated code.

2% in production calls vs 2026-W37 (187 → 191)

All of google.golang.org/grpc/metadata → Docs on pkg.go.dev ↗

prod calls
191
non-test, non-generated
all calls
441
total callsites
modules
75
distinct callers
in loop
1%
of prod calls
in tests
56%
248 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 function18%A direct call to an exported package function, resolved by type.
  • Package function (by syntax)82%A package function in a module outside the crawl, keyed by import path.

who calls this

Notable callers

Production calls into NewOutgoingContext 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 441, prioritizing in-loop and non-test usage. We link to source, never display it.

NewOutgoingContext · 12 of 441 callsites

top callers

The modules that reach for it

The modules that call NewOutgoingContext most in this snapshot.

  • google.golang.org/grpc8018%
  • github.com/grpc/grpc-go7717%
  • github.com/dapr/dapr235%
  • github.com/temporalio/temporal225%
  • go.temporal.io/server225%

siblings

More from google.golang.org/grpc/metadata

The other most-called functions in this package. See all →