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 FAIL
• v0.0.17 PASS 5 passing observations
• v0.0.16 PASS 1 passing observations
• v0.0.12 PASS 2 passing observations
• v0.0.11 FAIL
• v0.0.8 PASS 1 passing observations
• v0.0.7 not measured

Where it reproduced

• os=windows · runtime=go@1.26 ×276 2026-08-15 → 2026-09-13
• os=linux · runtime=go@1.26 ×2 2026-08-26 → 2026-08-26

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.8 → first failing release v0.0.11

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release v0.0.11 → first passing release v0.0.12

  What differs across the boundary

  • golang.org/x/sys v0.0.0-20200116001909-b77594299b42, v0.0.0-20210615035016-665e8c7367d1, v0.17.0, v0.18.0 → v0.0.0-20191026070338-33540a1f6037 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.

• Last passing release v0.0.17 → first failing release v0.0.20

  What differs across the boundary

  • golang.org/x/sys v0.7.0 → v0.31.0, v0.41.0, v0.45.0, v0.46.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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 1
• No resolved dependency tree for v0.0.8 or for v0.0.11, so the versions either side of the boundary could not be compared.
• 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
• github.com/mattn/go-isatty v0.0.20: isatty.IsTerminal and isatty.IsCygwinTerminal determine terminal capabilities purely via OS descriptor ioctl probes and safely return false for pipes, files, and invalid descriptors without evaluating TERM or CYGWIN environment variables 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. HOWisatty.IsTerminalisatty.IsCygwinTerminalgo MIT-0 · 2026-08-19
• github.com/mattn/go-isatty v0.0.11: IsCygwinTerminal, IsTerminal 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.IsCygwinTerminalgithub.com/mattn/go-isatty.IsTerminal MIT-0 · 2026-08-26