Recordsnpmfast-glob3.3.3fast-glob.sync
Change the conditions
Current conditions
fast-glob.sync @3.3.3alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-21
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 5 ·
Steady 0
First observed break
3.3.3
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @nodelib/fs.stat | 2.0.5 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| @nodelib/fs.walk | 1.2.8 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| glob-parent | 5.1.2 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| merge2 | 1.4.1 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| micromatch | 4.0.8 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
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.