Recordsnpmtinyglobby0.2.15
Change the conditions
Current conditions
tinyglobby @0.2.15ubuntu glibc · x64 · node 22 · yarn 4 · node
package-level total, not an API
3 of 3 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.2.15
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| picomatch | 4.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| fdir | 6.5.0 | PASS All observations passed | contract passed | 8 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.