CodeSampleX

Recordsnpmraw-body2.5.2

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

Current conditions

raw-body @2.5.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.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

2.5.2

linux · node@22.23 · moduleSystem=esm · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
http-errors 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
iconv-lite 0.4.24 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
bytes 3.1.2 PASS All observations passed contract passed 16 project-days
unpipe 1.0.0 PASS All observations passed contract passed 16 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.

Library3.0.22.5.32.5.22.5.1
http-errors 2.0.1 2.0.1 2.0.0 2.0.0
iconv-lite 0.7.3 0.4.24 0.4.24 0.4.24
bytes 3.1.2 3.1.2 3.1.2 3.1.2
unpipe 1.0.0 1.0.0 1.0.0 1.0.0

Moved: 2 · unchanged at every release: 2

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