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

Where it was measured

PASS means the release recorded a passing observation at PROCESS_START 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 not measured
• v0.0.17 not measured
• v0.0.16 not measured

Where it reproduced

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

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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.
• The captured output could not establish: diagnostic-missing.
• No release in this window recorded a passing observation at PROCESS_START.
• Releases in this window never measured at PROCESS_START: 3
• 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