Records/golang/github.com/cenkalti/backoff/v5/failure issue

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.

• v5.0.3 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-09-02 → 2026-09-02

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/cenkalti/backoff/v5 v5.0.3: ConstantBackOff 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/cenkalti/backoff/v5.ConstantBackOff MIT-0 · 2026-09-16
• github.com/cenkalti/backoff/v5 v5.0.3: PermanentError 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/cenkalti/backoff/v5.PermanentError MIT-0 · 2026-09-15
• github.com/cenkalti/backoff/v5 v5.0.3: NewTicker 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/cenkalti/backoff/v5.NewTicker MIT-0 · 2026-09-15