Recordsnpmtinyglobby
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| node 24 | node 22 | node (version not recorded) | |
|---|---|---|---|
| tinyglobby | 78%616 | 97%303 | — |
| glob | 100%1 | ||
| globSync | 100%1 | ||
| tinyglobby.convertPathToPattern | 100%1 | ||
| tinyglobby.escapePath | 100%1 | ||
| tinyglobby.glob | 100%1 |
Showing the environments with the most evidence.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.2.17
executionContext=node
40 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| 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.
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.