gopkg.in/yaml.v3.Unmarshal
third-partyThe 1247th most-called third-party function by production calls. Called 828 times across 119 modules; 504 of those run outside tests and generated code.
0% in production calls vs 2026-W37 (503 → 504)
- prod calls
- 504
- non-test, non-generated
- all calls
- 828
- total callsites
- modules
- 119
- distinct callers
- in loop
- 5%
- of prod calls
- in tests
- 39%
- 323 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.
- Package function (by syntax)<1%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into Unmarshal from notable Go projects. Open one on the map to see what else it hammers.
- Grafana 17 3%
- Cortex 10 2%
- GitHub CLI 5 <1%
- Istio 4 <1%
- Docker 3 <1%
where it's called
Callsites in the wild
12 representative callsites of 828, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
-
coder/coder @v0.27.3
in loop - in loop
- in loop
- in loop
top callers
The modules that reach for it
The modules that call Unmarshal most in this snapshot.
- github.com/GoogleContainerTools/skaffold/v214618%
- github.com/bytebase/bytebase8210%
- gopkg.in/yaml.v3364%
- github.com/sipeed/picoclaw334%
- github.com/crowdsecurity/crowdsec243%
siblings
More from gopkg.in/yaml.v3
The other most-called functions in this package. See all →