Recordsnpm@nodelib/fs.walk1.2.8
Change the conditions
Current conditions
@nodelib/fs.walk @1.2.8alpine musl · x64 · node 22 · npm · node
package-level total, not an API
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 (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 2 ·
Steady 0
First observed break
1.2.8
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:e51205820175ec6764f2985b095f56e601a16644e6bfc6acf5f862a256f0db5e
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @nodelib/fs.scandir | 2.1.5 | FAIL Linked failure observed on this release | contract passed | 1 project-day |
| fastq | 1.19.1 | 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.