CodeSampleX

Recordsnpmglob7.2.3

Change the conditions
Fixed
Runtimenode 22 Architecturex64 Package managernpm 11
Filter OSwindows 11 Package version7.2.3 Symbolwhole package Execution contextnode Clear filters

Current conditions

glob @7.2.3windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

18 of 20 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
18 / 20
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-24

Dependencies

LibraryVersionMeasured thereProjects
fs.realpath 1.0.0 contract passed 12 project-days
inflight 1.0.6 contract passed 11 project-days
inherits 2.0.4 contract passed 11 project-days
minimatch 3.1.5 contract passed 11 project-days
once 1.4.0 contract passed 11 project-days
path-is-absolute 1.0.1 contract passed 11 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.5.08.1.07.2.3
minimatch 9.0.9 5.1.9 3.1.5
foreground-child 3.3.1
fs.realpath 1.0.0 1.0.0
inflight 1.0.6 1.0.6
inherits 2.0.4 2.0.4
jackspeak 3.4.3
minipass 7.1.3
once 1.4.0 1.4.0
package-json-from-dist 1.0.1
path-is-absolute 1.0.1
path-scurry 1.11.1

Moved: 1 · unchanged at every release: 10

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