Recordsgolanghonnef.co/go/toolsfailure issue
Failure signature
UNKNOWN exit 1 ERROR Evidence gap ×1
go: downloading go.uber.org/zap v1.13.0 · verifying go.uber.org/zap@v1.13.0: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token>
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:cc6da42c69d5…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.0.1-2019.2.3 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-15 → 2026-09-15
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.
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: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- honnef.co/go/tools v0.0.1-2019.2.3 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. HOW MIT-0 · 2026-09-15