CodeSampleX

Recordsnpmminimatch10.1.1minimatch.escape

Change the conditions
Fixed
Runtimenode 24 Symbolminimatch.escape
Filter OSwindows 11 Package version10.1.1 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

minimatch.escape @10.1.1windows 11 · x64 · node 24 · npm 11 · node

4 of 4 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

10.1.1

linux · node@22.23 · moduleSystem=cjs · executionContext=node

29 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

View exact conditions View failure cluster
Library Version Health Measured there Projects
@isaacs/brace-expansion 5.0.0 PASS All observations passed builds observed 1 project-day
@isaacs/brace-expansion 5.0.1 PASS All observations passed contract passed 2 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library10.2.610.2.510.1.19.0.99.0.55.1.93.1.53.1.2
brace-expansion 5.0.8 5.0.9 — 2.0.2 2.0.2 2.1.7 1.1.21 1.1.12
@isaacs/brace-expansion — — 5.0.0 — — — — —

Moved: 1 · unchanged at every release: 1

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters