github.com/go-viper/mapstructure/v2.Decode
third-partyThe 5789th most-called third-party function by production calls. Called 211 times across 21 modules; 103 of those run outside tests and generated code.
No change in production calls since 2026-W37.
All of github.com/go-viper/mapstructure/v2 → Docs on pkg.go.dev ↗
- prod calls
- 103
- non-test, non-generated
- all calls
- 211
- total callsites
- modules
- 21
- distinct callers
- in loop
- 11%
- of prod calls
- in tests
- 51%
- 108 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 Decode from notable Go projects. Open one on the map to see what else it hammers.
- Grafana 41 40%
- Consul 15 15%
- Kubernetes 4 4%
- Nomad 2 2%
- containerd 1 <1%
where it's called
Callsites in the wild
12 representative callsites of 211, 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
- in loop
- in loop
- in loop
-
duckdb/duckdb-go/v2 @v2.10505.0
in loop test
top callers
The modules that reach for it
The modules that call Decode most in this snapshot.
- github.com/go-viper/mapstructure/v29645%
- github.com/grafana/alloy5024%
- github.com/hashicorp/consul157%
- github.com/anchore/syft126%
- github.com/aquasecurity/trivy84%