CodeSampleX

Recordsnpmc12

no sample at this coordinate yet

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 version3.1.0
Filter Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters
OS × Runtime
1○ 12026-09-16
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 1 · Steady 18

First observed break

3.1.0

windows · node@24.13 · executionContext=node · moduleSystem=cjs

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
chokidar 4.0.3 PASS All observations passed contract passed 4 project-days
confbox 0.2.2 PASS All observations passed contract passed 3 project-days
confbox 0.2.4 PASS All observations passed builds observed 1 project-day
defu 6.1.4 PASS All observations passed contract passed 3 project-days
defu 6.1.7 PASS All observations passed builds observed 1 project-day
dotenv 16.6.1 PASS All observations passed contract passed 4 project-days
exsolve 1.0.8 PASS All observations passed contract passed 3 project-days
exsolve 1.1.1 PASS All observations passed builds observed 1 project-day
giget 2.0.0 PASS All observations passed contract passed 4 project-days
jiti 2.6.1 PASS All observations passed contract passed 3 project-days
jiti 2.7.0 PASS All observations passed contract passed 1 project-day
ohash 2.0.11 PASS All observations passed contract passed 3 project-days
ohash 2.0.12 PASS All observations passed builds observed 1 project-day
pathe 2.0.3 PASS All observations passed contract passed 4 project-days
perfect-debounce 1.0.0 PASS All observations passed contract passed 4 project-days
pkg-types 2.3.0 PASS All observations passed contract passed 3 project-days
pkg-types 2.3.3 PASS All observations passed builds observed 1 project-day
rc9 2.1.2 PASS All observations passed contract passed 4 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.