CodeSampleX

Recordsnpmtinyglobby0.2.17

Change the conditions
Fixed
Runtimenode (version not recorded) Package managernpm
Filter OSwindows 11 Package version0.2.17 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

tinyglobby @0.2.17windows 11 · x64 · node (version not recorded) · 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
1
Independent reporting peers
1
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

0.2.17

executionContext=node

40 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

View exact conditions View failure cluster
Library Version Health Measured there Projects
picomatch 4.0.4 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
picomatch 4.0.5 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
picomatch 4.0.7 CANDIDATE Correlated change; unproven combination contract passed 135 project-days
fdir 6.5.0 PASS All observations passed contract passed 167 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.

Library0.2.170.2.15
picomatch 4.0.4 4.0.3
fdir 6.5.0 6.5.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