Recordsnpmexpress
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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
Dependency changes observed: 19. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| accepts | 1.3.8 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| body-parser | 1.20.3 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| content-disposition | 0.5.4 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| cookie | 0.6.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| cookie-signature | 1.0.6 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| debug | 2.6.9 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| encodeurl | 2.0.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| finalhandler | 1.3.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| fresh | 0.5.2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| http-errors | 2.0.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| merge-descriptors | 1.0.3 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| path-to-regexp | 0.1.10 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| proxy-addr | 2.0.7 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| qs | 6.13.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| range-parser | 1.2.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| send | 0.19.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| serve-static | 1.16.2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| statuses | 2.0.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| type-is | 1.6.18 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| array-flatten | 1.1.1 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| utils-merge | 1.0.1 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| content-type | 1.0.5 | PASS All observations passed | contract passed | 1 project-day |
| depd | 2.0.0 | PASS All observations passed | contract passed | 1 project-day |
| escape-html | 1.0.3 | PASS All observations passed | contract passed | 1 project-day |
| etag | 1.8.1 | PASS All observations passed | contract passed | 1 project-day |
| methods | 1.1.2 | PASS All observations passed | contract passed | 1 project-day |
| on-finished | 2.4.1 | PASS All observations passed | contract passed | 1 project-day |
| parseurl | 1.3.3 | PASS All observations passed | contract passed | 1 project-day |
| safe-buffer | 5.2.1 | PASS All observations passed | contract passed | 1 project-day |
| setprototypeof | 1.2.0 | PASS All observations passed | contract passed | 1 project-day |
| vary | 1.1.2 | PASS All observations passed | 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.
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.
Moved: 19 · unchanged at every release: 15
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.