Recordsgolanggopkg.in/yaml.v3v3.0.1gopkg.in/yaml.v3.Unmarshal
OS × runtime at a glance
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.
Published samples
- gopkg.in/yaml.v3 v3.0.1: Unmarshal commented block sequences with malformed syntax without nil pointer dereference panic fixed in gopkg.in/yaml.v3 v3.0.1 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. HOWgopkg.in/yaml.v3.Unmarshalgo MIT-0 · 2026-08-16
- gopkg.in/yaml.v3 v3.0.1: Unmarshal YAML documents into yaml.Node AST where top-level mappings are wrapped in a DocumentNode and mapping entries are stored as a flat slice of alternating key and value nodes. 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. HOWyaml.Nodeyaml.Unmarshalyaml.Node.Decodego MIT-0 · 2026-08-17
- gopkg.in/yaml.v3 v3.0.1: Marshal and unmarshal YAML config in Go with yaml.v3 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. HOWyaml.Unmarshalyaml.Marshalgo 1.26 MIT-0 · 2026-08-13
Compatibility matrix
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 · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-14 |
| go 1.26 · Go · gomod · linux musl · docker
Verified: CONTRACT 2✓
|
LOW | 0 | 2 | 100% | 0 · 1✓ | 2026-08-18 |
snapshot · 2026-08-31
Failure clusters
-
observed PROJECT_TEST Evidence gap ×3 v3.0.1 os=windows · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-19 · Last seen: 2026-08-19Diagnostic re-verification candidate