CodeSampleX

Recordsgolanggolang.org/x/sysv0.35.0

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

62026-08-29
ubuntu glibc
golang.org/x/sys/unix.Close 100%2
golang.org/x/sys/unix.Getpid 100%2
golang.org/x/sys/unix.NsecToTimeval 100%2
golang.org/x/sys/unix.Pipe 100%2
golang.org/x/sys/unix.Read 100%2
golang.org/x/sys/unix.TimevalToNsec 100%2

Showing the environments with the most evidence.

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment Confidence Observations Verified Pass rate Peers Last seen
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 2✓ — Usage: USED 2✓
LOW 2 +2 0 100% 1 2026-08-29

Symbols