Recordsgolanggithub.com/go-logfmt/logfmtv0.6.0github.com/go-logfmt/logfmt.MarshalKeyvals
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
- github.com/go-logfmt/logfmt v0.6.0: MarshalKeyvals, NewDecoder 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. HOWgithub.com/go-logfmt/logfmt.MarshalKeyvalsgithub.com/go-logfmt/logfmt.NewDecoder MIT-0 · 2026-08-27
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 1✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 1 | 1 | 50% | 1 | 2026-08-31 |
| go 1.26 · Go · go · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
snapshot · 2026-08-31
Failure clusters
-
observed PROJECT_PROCESS Evidence gap ×3 v0.6.0 os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:6ed4679e28a1…expected logfmt.ErrUnsupportedKeyType for int key, got <nil> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.6.0 os=linux · runtime=go@1.26 github.com/go-logfmt/logfmt.MarshalKeyvals sha256:7d69c4f6d69b…assertion 5 failed: expected ErrInvalidKey, got <nil> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:7e1230015d91…expected logfmt.ErrInvalidKey for key with <str>, got <nil> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate