Recordsnpmbody-parser
there is a sample for this release and API (3)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
First observed break
1.20.3
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| content-type | 1.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| debug | 2.6.9 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| http-errors | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| iconv-lite | 0.4.24 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| qs | 6.13.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| raw-body | 2.5.2 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| type-is | 1.6.18 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| bytes | 3.1.2 | PASS All observations passed | contract passed | 11 project-days |
| depd | 2.0.0 | PASS All observations passed | contract passed | 11 project-days |
| destroy | 1.2.0 | PASS All observations passed | contract passed | 11 project-days |
| on-finished | 2.4.1 | PASS All observations passed | contract passed | 11 project-days |
| unpipe | 1.0.0 | PASS All observations passed | contract passed | 11 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.
| Library | 2.3.0 | 1.20.6 | 1.20.3 | 1.20.2 | 1.20.1 |
|---|---|---|---|---|---|
| content-type | 2.0.0 | 1.0.5 | 1.0.5 | 1.0.5 | 1.0.5 |
| debug | 4.4.3 | 2.6.9 | 2.6.9 | 2.6.9 | 2.6.9 |
| http-errors | 2.0.1 | 2.0.1 | 2.0.0 | 2.0.0 | 2.0.0 |
| iconv-lite | 0.7.3 | 0.4.24 | 0.4.24 | 0.4.24 | 0.4.24 |
| qs | 6.16.0 | 6.15.3 | 6.13.0 | 6.11.0 | 6.11.0 |
| raw-body | 3.0.2 | 2.5.3 | 2.5.2 | 2.5.2 | 2.5.1 |
| type-is | 2.1.0 | 1.6.18 | 1.6.18 | 1.6.18 | 1.6.18 |
| bytes | 3.1.2 | 3.1.2 | 3.1.2 | 3.1.2 | 3.1.2 |
| depd | — | 2.0.0 | 2.0.0 | 2.0.0 | 2.0.0 |
| destroy | — | 1.2.0 | 1.2.0 | 1.2.0 | 1.2.0 |
| on-finished | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 |
| unpipe | — | 1.0.0 | 1.0.0 | 1.0.0 | 1.0.0 |
Moved: 7 · unchanged at every release: 5
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.