Records/golang/github.com/go-logfmt/logfmt/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v0.6.1 not measured
• v0.6.0 FAIL
• v0.5.1 PASS 2 passing observations
• v0.5.0 PASS 2 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-09-02 → 2026-09-02

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release v0.5.1 → first failing release v0.6.0

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• Releases in this window never measured at PROJECT_COMPILE: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/go-logfmt/logfmt v0.6.0: NewEncoder Built ? 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. HOWlogfmt.NewEncodergo 1.26.6 MIT-0 · 2026-09-02
• github.com/go-logfmt/logfmt v0.6.0: NewDecoder Built ? 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. HOWlogfmt.NewDecodergo 1.26.6 MIT-0 · 2026-09-02
• github.com/go-logfmt/logfmt v0.6.0: MarshalKeyvals Built ? 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. HOWlogfmt.MarshalKeyvalsgo 1.26.6 MIT-0 · 2026-09-02