Recordsnpmglob7.2.3
Change the conditions
Current conditions
glob @7.2.3windows 11 · x64 · node 22 · pnpm 10 · node
package-level total, not an API
11 of 14 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
- 11 / 14
- Contract verifications
- nothing at this coordinate
- Usage records
- 72
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 3
- Last recorded
- 2026-08-24
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.2.3
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| minimatch | 3.1.2 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| minimatch | 3.1.5 | CANDIDATE Correlated change; unproven combination | contract passed | 70 project-days |
| fs.realpath | 1.0.0 | PASS All observations passed | contract passed | 66 project-days |
| inflight | 1.0.6 | PASS All observations passed | contract passed | 64 project-days |
| inherits | 2.0.4 | PASS All observations passed | contract passed | 68 project-days |
| once | 1.4.0 | PASS All observations passed | contract passed | 68 project-days |
| path-is-absolute | 1.0.1 | PASS All observations passed | contract passed | 63 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.
| Library | 13.0.6 | 13.0.0 | 10.5.0 | 10.3.10 | 8.1.0 | 7.2.3 |
|---|---|---|---|---|---|---|
| jackspeak | — | — | 3.4.3 | 2.3.6 | — | — |
| minimatch | 10.2.5 | 10.1.1 | 9.0.5 | 9.0.5 | 5.1.9 | 3.1.2 |
| minipass | 7.1.3 | 7.1.2 | 7.1.2 | 7.1.2 | — | — |
| path-scurry | 2.0.2 | 2.0.1 | 1.11.1 | 1.11.1 | — | — |
| foreground-child | — | — | 3.3.1 | 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 |
| once | — | — | — | — | 1.4.0 | 1.4.0 |
| package-json-from-dist | — | — | 1.0.1 | — | — | — |
| path-is-absolute | — | — | — | — | — | 1.0.1 |
Moved: 4 · unchanged at every release: 7
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
-
observed PROCESS_START process start failed Evidence gap ×10 7.2.3 → 8.1.0 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_TEST Evidence gap ×8 7.2.3 → 8.1.0 → 10.5.0 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×4 7.2.3 → 8.1.0 → 10.5.0 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-21Diagnostic re-verification candidate