Recordsnpmpicomatchfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×41
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-31 · Last seen: 2026-09-16
sha256:c12549970456…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×27 2026-08-31 → 2026-09-14
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×11 2026-09-08 → 2026-09-08
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-09-16 → 2026-09-16
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-09-13 → 2026-09-13
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: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- picomatch 4.0.7: Compile glob patterns into regular expressions with picomatch.makeRe 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. HOWpicomatch.makeRe MIT-0 · 2026-08-27
- picomatch 4.0.5: Extract static base directory and glob pattern with picomatch.scan 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. HOWpicomatch.scan MIT-0 · 2026-08-26
- picomatch 4.0.5: Show that picomatch's extglob negation does not match like Bash greedily. 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. HOWpicomatch.isMatchnode MIT-0 · 2026-08-17
- picomatch 4.0.5: Exclude files from a glob match when adding a "!pattern" to the array does nothing 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. FIXpicomatchignorenode 22 MIT-0 · 2026-08-13
- picomatch 2.3.2 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
- picomatch 2.3.2 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-19