Recordsgolanggithub.com/go-logr/stdrfailure issue
Failure signature
UNKNOWN exit 1 ERROR Evidence gap ×13
verifying go.opentelemetry.io/otel@v1.43.0/go.mod: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token> · SECURITY ERROR
Evidence quality: complete · go · unclassified-diagnostic · outer go mod, go run · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-09-01
sha256:69d280c75213…
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.
- v1.2.2 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×13 2026-08-30 → 2026-09-01
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
- github.com/go-logr/stdr v1.2.2: Create a logr.Logger using stdr.New with stdlib log.Logger and verify Info/Error logging 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. HOWstdr.New MIT-0 · 2026-08-18