Recordsnpmlodash.escaperegexpfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
Contract test failed: Error: Command node exited with code 2 · at CustomBaseUpdater.spawnSyncLog <path>:<n>:<n>) · at main (<path>:<n>:<n>) …
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:91bb8f54cd90…
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.
- 4.1.2 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-29 → 2026-08-29
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
- lodash.escaperegexp 4.1.2: escapeRegExp 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. HOWescapeRegExplodash.escaperegexpnode 22.23.2 MIT-0 · 2026-08-28