Skip to content
callcount

github.com/spf13/viper.BindPFlag

third-party

The 4149th most-called third-party function by production calls. Called 144 times across 15 modules; 144 of those run outside tests and generated code.

All of github.com/spf13/viper → Docs on pkg.go.dev ↗

prod calls
144
non-test, non-generated
all calls
144
total callsites
modules
15
distinct callers
in loop
1%
of prod calls
in tests
0%
0 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 function (by syntax)100%A package function in a module outside the crawl, keyed by import path.

who calls this

Notable callers

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

BindPFlag · 12 of 144 callsites

top callers

The modules that reach for it

The modules that call BindPFlag most in this snapshot.

  • github.com/codenotary/immudb3826%
  • github.com/github/github-mcp-server2819%
  • github.com/navidrome/navidrome2014%
  • github.com/drakkan/sftpgo1611%
  • github.com/usememos/memos107%

siblings

More from github.com/spf13/viper

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