Recordsnpmcaniuse-litefailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×12
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-20 · Last seen: 2026-08-29
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 1.0.30001810 PASS 374 passing observations
- 1.0.30001809 FAIL
- 1.0.30001806 not measured
- 1.0.30001793 not measured
- 1.0.30001761 PASS 11 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×8 2026-08-20 → 2026-08-29
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×4 2026-08-21 → 2026-08-23
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 1.0.30001761 → first failing release 1.0.30001809
Releases between them never measured at this stage: 2
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 1.0.30001809 → first passing release 1.0.30001810
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_PROCESS: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- caniuse-lite 1.0.30001809 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. HOW MIT-0 · 2026-08-26