Recordsgolanggolang.org/x/netv0.42.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
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 |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 3✓ — Verified: CONTRACT 3✓
|
LOW | 4 +3 | 3 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 18✓ — Usage: USED 22✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 18 +22 | 1 | 95% | 1 | 2026-09-15 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×4 v0.0.0-20210226172049-e18ecbb05110 → v0.37.0 → v0.42.0 → v0.53.0 os=linux · runtime=go@1.26 sha256:042f6e977a16…go: updates to go.mod needed; to update it: · go mod tidygo · unclassified-diagnostic · outer go run, go test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-15Diagnostic re-verification candidate
Symbols
- golang.org/x/net/html.Attribute
- golang.org/x/net/html.CommentNode
- golang.org/x/net/html.DoctypeNode 1 1 of 2 runs passed
- golang.org/x/net/html.DocumentNode 1 1 of 2 runs passed
- golang.org/x/net/html.ElementNode 0 of 1 runs passed
- golang.org/x/net/html.ErrorNode
- golang.org/x/net/html.Node
- golang.org/x/net/html.NodeType
- golang.org/x/net/html.Parse 0 of 1 runs passed
- golang.org/x/net/html.RawNode
- golang.org/x/net/html.Render
- golang.org/x/net/html.TextNode
Published samples
- golang.org/x/net v0.42.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo 1.26.6 MIT-0 · 2026-09-15