Recordsgolanggoogle.golang.org/protobufv1.36.12google.golang.org/protobuf/encoding/prototext.UnmarshalOptions
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
- google.golang.org/protobuf v1.36.12: Control JSON formatting and parsing of Protocol Buffers messages using protojson MarshalOptions and UnmarshalOptions 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. HOWgoogle.golang.org/protobuf/encoding/protojson.Marshalgoogle.golang.org/protobuf/encoding/protojson.MarshalOptionsgoogle.golang.org/protobuf/encoding/protojson.Unmarshalgoogle.golang.org/protobuf/encoding/protojson.UnmarshalOptionsgo MIT-0 · 2026-08-17
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 · linux glibc
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-29 |
| go 1.26 · Go · go · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v1.36.12 os=linux · runtime=go@1.26 sha256:81f3ab761904…test/contract.go:<n>:<n>: declared and not used: nilMsggo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.36.12 os=linux · runtime=go@1.26 sha256:5684c2833557…FAIL: expected error when marshaling untyped nil proto.Message · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate