Recordsnpmcaniuse-litefailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
> wslpad@1.0.2 lint · > eslint . · <path> · 77:<n> error Unexpected control character(s) in regular expression: \x1b no-control-regex
Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:6cf9c24b033d…
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.
- 1.0.30001810 not measured
- 1.0.30001809 not measured
- 1.0.30001806 FAIL
- 1.0.30001793 not measured
- 1.0.30001761 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
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.
- Releases in this window never measured at UNKNOWN: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- caniuse-lite 1.0.30001806 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-27
- caniuse-lite 1.0.30001806 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-21