Recordsnpmexpress
Change the conditions
Current conditions
express @5.1.0windows 11 · x64 · node 24 · npm 11 · node
3 of 13 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (7)
- Project observations
- 3 / 13
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 2
- Failures with a captured fingerprint
- 0 / 10
- Last recorded
- 2026-08-14
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
3 of 13 passed
Observed — real project builds reported from this coordinate.
-
express.json
2 of 9 passed
Observed — real project builds reported from this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| accepts | 2.0.0 | contract passed | 2 project-days |
| body-parser | 2.3.0 | contract passed | 2 project-days |
| content-disposition | 1.1.0 | contract passed | 2 project-days |
| content-type | 1.0.5 | contract passed | 2 project-days |
| cookie | 0.7.2 | contract passed | 2 project-days |
| cookie-signature | 1.2.2 | contract passed | 2 project-days |
| debug | 4.4.3 | contract passed | 2 project-days |
| encodeurl | 2.0.0 | contract passed | 2 project-days |
| escape-html | 1.0.3 | contract passed | 2 project-days |
| etag | 1.8.1 | contract passed | 2 project-days |
| finalhandler | 2.1.1 | contract passed | 2 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 | 5.2.1 | 5.1.0 |
|---|---|---|
| accepts | 2.0.0 | 2.0.0 |
| body-parser | 2.3.0 | 2.3.0 |
| content-disposition | 1.1.0 | 1.1.0 |
| content-type | 1.0.5 | 1.0.5 |
| cookie | 0.7.2 | 0.7.2 |
| cookie-signature | 1.2.2 | 1.2.2 |
| debug | 4.4.3 | 4.4.3 |
| depd | 2.0.0 | — |
| encodeurl | 2.0.0 | 2.0.0 |
| escape-html | 1.0.3 | 1.0.3 |
| etag | 1.8.1 | 1.8.1 |
| finalhandler | 2.1.1 | 2.1.1 |
| fresh | 2.0.0 | — |
| http-errors | 2.0.1 | — |
| merge-descriptors | 2.0.0 | — |
| mime-types | 3.0.2 | — |
| on-finished | 2.4.1 | — |
| once | 1.4.0 | — |
| parseurl | 1.3.3 | — |
| proxy-addr | 2.0.7 | — |
| qs | 6.15.3 | — |
| range-parser | 1.3.0 | — |
| router | 2.2.0 | — |
| send | 1.2.1 | — |
| serve-static | 2.2.1 | — |
| statuses | 2.0.2 | — |
| type-is | 2.1.0 | — |
| vary | 1.1.2 | — |
Moved: 0 · unchanged at every release: 28
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.