CodeSampleX

Recordsnpm@nodelib/fs.walk

there is a sample for this release and API (1)

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version1.2.8
Filter Symbolwhole package Architecturex64 Execution contextnode libcmusl Clear filters
OS × Runtime
1 12026-09-01
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

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.