CodeSampleX

Recordsnpmbody-parser2.3.0

Change the conditions
Fixed
OSalpine musl Package version2.3.0 Symbolwhole package
Filter Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

body-parser @2.3.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
2 / 2
Contract verifications
1 / 1
Usage records
3
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 9 · Steady 2

First observed break

2.3.0

windows · node@24.13 · executionContext=node · moduleSystem=esm

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
content-type 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
content-type 2.1.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
debug 4.4.3 CANDIDATE Correlated change; unproven combination contract passed 26 project-days
http-errors 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
iconv-lite 0.7.3 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
qs 6.15.3 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
qs 6.16.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
raw-body 3.0.2 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
type-is 2.1.0 CANDIDATE Correlated change; unproven combination contract passed 26 project-days
bytes 3.1.2 PASS All observations passed contract passed 27 project-days
on-finished 2.4.1 PASS All observations passed contract passed 27 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.

Library2.3.01.20.61.20.31.20.21.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.

Recent failure clusters