Recordsgolanggithub.com/cespare/xxhash/v2failure issue
Failure signature
UNKNOWN exit 1 ERROR Evidence gap ×2
verifying go.opentelemetry.io/proto/otlp@v1.10.0/go.mod: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token> · SECURITY ERROR
Evidence quality: complete · go · unclassified-diagnostic · outer go mod · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:ee3d1e9b170c…
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.
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-08-31 → 2026-08-31
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.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/cespare/xxhash/v2 v2.3.0: Sum64, Sum64String, New 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/cespare/xxhash/v2.Sum64github.com/cespare/xxhash/v2.Sum64Stringgithub.com/cespare/xxhash/v2.New MIT-0 · 2026-08-18