CodeSampleX

Recordsnpmexpress

Change the conditions
Fixed
Runtimenode 22 Package version4.22.2 Execution contextnode
Filter OSalpine musl Architecturex64 Package managernpm libcmusl Clear filters

Current conditions

express @4.22.2alpine musl · x64 · node 22 · npm · node

3 of 3 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
6 / 6
Contract verifications
3 / 3
Usage records
4
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08
Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 20 · Unknown 2 · Steady 9

Dependency changes observed: 20. 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.6 CHANGED Version changed, no linked failure builds observed 1 project-day
content-disposition 0.5.4 CHANGED Version changed, no linked failure contract passed 1 project-day
content-type 1.0.5 CHANGED Version changed, no linked failure contract passed 1 project-day
cookie 0.7.2 CHANGED Version changed, no linked failure contract passed 1 project-day
cookie-signature 1.0.7 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.2 CHANGED Version changed, no linked failure builds observed 1 project-day
fresh 0.5.2 CHANGED Version changed, no linked failure contract passed 1 project-day
http-errors 2.0.1 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.13 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.15.3 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.2 CHANGED Version changed, no linked failure builds observed 1 project-day
serve-static 1.16.3 CHANGED Version changed, no linked failure builds observed 1 project-day
statuses 2.0.2 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
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.

Library5.3.05.2.15.1.04.22.24.21.24.21.04.19.14.18.2
accepts 2.0.0 2.0.0 2.0.0 1.3.8 1.3.8 1.3.8 1.3.8 1.3.8
body-parser 2.3.0 2.3.0 2.3.0 1.20.6 1.20.3 1.20.3 1.20.2 1.20.1
content-disposition 2.0.1 1.1.0 1.1.0 0.5.4 0.5.4 0.5.4 0.5.4 0.5.4
content-type 2.1.0 1.0.5 1.0.5 1.0.5 1.0.5 1.0.5 1.0.5 1.0.5
cookie 0.7.2 0.7.2 0.7.2 0.7.2 0.7.1 0.6.0 0.6.0 0.5.0
cookie-signature 1.2.2 1.2.2 1.2.2 1.0.7 1.0.6 1.0.6 1.0.6 1.0.6
debug 4.4.3 4.4.3 4.4.3 2.6.9 2.6.9 2.6.9 2.6.9 2.6.9
encodeurl 2.0.0 2.0.0 2.0.0 2.0.0 2.0.0 2.0.0 1.0.2 1.0.2
finalhandler 2.1.1 2.1.1 2.1.1 1.3.2 1.3.1 1.3.1 1.2.0 1.2.0
fresh 2.0.0 2.0.0 2.0.0 0.5.2 0.5.2 0.5.2 0.5.2 0.5.2
http-errors 2.0.1 2.0.1 2.0.1 2.0.1 2.0.0 2.0.0 2.0.0 2.0.0
merge-descriptors 2.0.0 2.0.0 2.0.0 1.0.3 1.0.3 1.0.3 1.0.1 1.0.1
path-to-regexp — — 8.4.2 0.1.13 0.1.12 0.1.10 0.1.7 0.1.7
proxy-addr 2.0.8 2.0.8 2.0.7 2.0.7 2.0.7 2.0.7 2.0.7 2.0.7
qs 6.16.1 6.16.0 6.15.3 6.15.3 6.13.0 6.13.0 6.11.0 6.11.0
range-parser 1.3.0 1.3.0 1.3.0 1.2.1 1.2.1 1.2.1 1.2.1 1.2.1
send 1.2.1 1.2.1 1.2.1 0.19.2 0.19.0 0.19.0 0.18.0 0.18.0
serve-static 2.2.1 2.2.1 2.2.1 1.16.3 1.16.2 1.16.2 1.15.0 1.15.0
statuses 2.0.2 2.0.2 2.0.2 2.0.2 2.0.1 2.0.1 2.0.1 2.0.1
type-is 2.1.0 2.1.0 2.1.0 1.6.18 1.6.18 1.6.18 1.6.18 1.6.18
array-flatten — — — 1.1.1 1.1.1 1.1.1 1.1.1 1.1.1
depd 2.0.0 2.0.0 — 2.0.0 2.0.0 2.0.0 2.0.0 2.0.0
escape-html 1.0.3 1.0.3 1.0.3 1.0.3 1.0.3 1.0.3 1.0.3 1.0.3
etag 1.8.1 1.8.1 1.8.1 1.8.1 1.8.1 1.8.1 1.8.1 1.8.1
methods — — — 1.1.2 1.1.2 1.1.2 1.1.2 1.1.2
mime-types 3.0.2 3.0.2 3.0.2 — — — — —
on-finished 2.4.1 2.4.1 2.4.1 2.4.1 2.4.1 2.4.1 2.4.1 2.4.1
once 1.4.0 1.4.0 1.4.0 — — — — —
parseurl 1.3.3 1.3.3 1.3.3 1.3.3 1.3.3 1.3.3 1.3.3 1.3.3
router 2.2.0 2.2.0 2.2.0 — — — — —
safe-buffer — — — 5.2.1 5.2.1 5.2.1 5.2.1 5.2.1
setprototypeof — — — 1.2.0 1.2.0 1.2.0 1.2.0 1.2.0
utils-merge — — — 1.0.1 1.0.1 1.0.1 1.0.1 1.0.1
vary 1.1.2 1.1.2 1.1.2 1.1.2 1.1.2 1.1.2 1.1.2 1.1.2

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.