Recordsnpm@isaacs/cliuifailure issue
Failure signature
PROJECT_TEST Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-21
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 8.0.2 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-17 → 2026-08-17
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.
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @isaacs/cliui 8.0.2: format multi-column terminal UI text with cliui 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. HOWnode 22.23.2 MIT-0 · 2026-08-28