Records/golang/github.com/mattn/go-isatty/failure issue

Where it was measured

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

• v0.0.24 FAIL
• v0.0.20 PASS 39 passing observations
• v0.0.17 PASS 5 passing observations
• v0.0.16 PASS 1 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27

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.0.20 → first failing release v0.0.24

  What differs across the boundary

  • golang.org/x/sys v0.31.0, v0.41.0, v0.45.0, v0.46.0 → v0.47.0 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 1 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/mattn/go-isatty v0.0.24: IsTerminal, IsCygwinTerminal 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. HOWgithub.com/mattn/go-isatty.IsTerminalgithub.com/mattn/go-isatty.IsCygwinTerminal MIT-0 · 2026-08-18