Recordsnpmexponential-backofffailure issue
Failure signature
UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 1 !== 2 · at Object.retry (<path>:<n>:<n>) · at BackOff.<anonymous> <path>:<n>:<n>)
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:96f4b8422887…
exponential-backoff.backOff
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.
- 3.1.3 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-30 → 2026-08-30
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
- exponential-backoff 3.1.3: backOff 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. HOWbackOffnode 22.23.2 MIT-0 · 2026-08-26