Recordsnpmglob10.5.0
Change the conditions
Current conditions
glob @10.5.0debian glibc · x64 · node 22 · npm · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
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
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
10.5.0
windows · node@24.13 · moduleSystem=cjs · executionContext=node
12 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| jackspeak | 3.4.3 | CANDIDATE Correlated change; unproven combination | 16 project-days | |
| minimatch | 9.0.5 | CANDIDATE Correlated change; unproven combination | 3 project-days | |
| minimatch | 9.0.9 | CANDIDATE Correlated change; unproven combination | 21 project-days | |
| minipass | 7.1.2 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| minipass | 7.1.3 | CANDIDATE Correlated change; unproven combination | 21 project-days | |
| path-scurry | 1.11.1 | CANDIDATE Correlated change; unproven combination | 16 project-days | |
| foreground-child | 3.3.1 | UNKNOWN No linked outcome measured | 17 project-days | |
| package-json-from-dist | 1.0.1 | UNKNOWN No linked outcome measured | 16 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 UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 7.2.3 → 10.5.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:054c93088b95…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 7.2.3 → 10.5.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a878372dcfe9…AssertionError [ERR_ASSERTION]: getVersion must return 30.4.2 · <str> !== <str> · at main (<path>:<n>:<n>) · at Object.<anonymous> (<path>:<n>:<n>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate