Records/npm/picomatch/failure issue

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.

• 4.0.7 FAIL
• 4.0.5 FAIL
• 4.0.4 PASS 4 passing observations
• 4.0.3 PASS 15 passing observations
• 2.3.2 FAIL
• 2.3.1 PASS 11 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×8 2026-08-23 → 2026-08-30
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×7 2026-08-20 → 2026-08-30
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-14 → 2026-08-14

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 2.3.1 → first failing release 2.3.2

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 2.3.2 → first passing release 4.0.3

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last passing release 4.0.4 → first failing release 4.0.5

  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.
• 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 Built ? 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 Built ? 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. Built ? 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 Built ? 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 Built ? 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 Built ? 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