Recordsnpmexpress5.3.0express
Change the conditions
Current conditions
express @5.3.0debian glibc · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-21
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.3.0
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:ef96efaca8ddfbeeab2a7eea64a1b583e926d75644ef751cb70b035ace5efbd5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| accepts | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| body-parser | 2.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| content-disposition | 2.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| content-type | 2.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| cookie | 0.7.2 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| cookie-signature | 1.2.2 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| debug | 4.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| encodeurl | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| finalhandler | 2.1.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| fresh | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| http-errors | 2.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| merge-descriptors | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| proxy-addr | 2.0.8 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| qs | 6.16.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| range-parser | 1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| send | 1.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| serve-static | 2.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| statuses | 2.0.2 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| type-is | 2.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
| depd | 2.0.0 | PASS All observations passed | contract passed | 42 project-days |
| escape-html | 1.0.3 | PASS All observations passed | contract passed | 42 project-days |
| etag | 1.8.1 | PASS All observations passed | contract passed | 42 project-days |
| mime-types | 3.0.2 | PASS All observations passed | contract passed | 42 project-days |
| on-finished | 2.4.1 | PASS All observations passed | contract passed | 42 project-days |
| once | 1.4.0 | PASS All observations passed | contract passed | 42 project-days |
| parseurl | 1.3.3 | PASS All observations passed | contract passed | 42 project-days |
| router | 2.2.0 | PASS All observations passed | contract passed | 42 project-days |
| vary | 1.1.2 | PASS All observations passed | contract passed | 42 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.
Moved: 20 · unchanged at every release: 14
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.
Recent failure clusters
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.3.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:ef96efaca8dd…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · undefined !== 123 · at <url> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-21 · Last seen: 2026-10-21