Skip to content
callcount

crypto/sha256.Sum256

standard library

The 556th most-called standard-library function by production calls. Called 2,105 times across 333 modules; 1,363 of those run outside tests and generated code.

All of crypto/sha256 → Docs on pkg.go.dev ↗

prod calls
1,363
non-test, non-generated
all calls
2,105
total callsites
modules
333
distinct callers
in loop
9%
of prod calls
in tests
35%
734 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.

estimate

Experimental

Estimated relative cost

Roughly 0.01× the estimated relative cost of fmt.Sprintf . Benchmarked at 157.5 ns/op × 1,363 production calls, normalized so fmt.Sprintf = 1.0.

This is not dollars and not a verdict. Per-op time depends heavily on inputs (argument sizes, contention, patterns), the benchmark ran on a single machine (darwin/arm64 (Apple Silicon), go1.26.0), and static call counts are not runtime frequency. How this is estimated →

who calls this

Notable callers

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

Sum256 · 12 of 2,105 callsites

top callers

The modules that reach for it

The modules that call Sum256 most in this snapshot.

  • github.com/codenotary/immudb1276%
  • github.com/sigstore/rekor804%
  • github.com/heroiclabs/nakama754%
  • github.com/esengine/DeepSeek-Reasonix643%
  • github.com/kubernetes/kubernetes462%

siblings

More from crypto/sha256

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