CodeSampleX

Recordsnpmbody-parser1.20.2

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

Current conditions

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

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 7 · Steady 5

Dependency changes observed: 7. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
content-type 1.0.5 CHANGED Version changed, no linked failure contract passed 3 project-days
debug 2.6.9 CHANGED Version changed, no linked failure contract passed 3 project-days
http-errors 2.0.0 CHANGED Version changed, no linked failure contract passed 3 project-days
iconv-lite 0.4.24 CHANGED Version changed, no linked failure contract passed 3 project-days
qs 6.11.0 CHANGED Version changed, no linked failure contract passed 3 project-days
raw-body 2.5.2 CHANGED Version changed, no linked failure contract passed 3 project-days
type-is 1.6.18 CHANGED Version changed, no linked failure contract passed 3 project-days
bytes 3.1.2 PASS All observations passed contract passed 3 project-days
depd 2.0.0 PASS All observations passed contract passed 3 project-days
destroy 1.2.0 PASS All observations passed contract passed 3 project-days
on-finished 2.4.1 PASS All observations passed contract passed 3 project-days
unpipe 1.0.0 PASS All observations passed contract passed 3 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: 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.