CodeSampleX

Recordsnpmsend1.2.1

Change the conditions
Fixed
OSdebian glibc Package version1.2.1
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

send @1.2.1debian glibc · 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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 5

First observed break

1.2.1

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

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

Library Version Health Measured there Projects
debug 4.4.3 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
encodeurl 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 26 project-days
fresh 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
http-errors 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 26 project-days
range-parser 1.3.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
statuses 2.0.2 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
escape-html 1.0.3 PASS All observations passed contract passed 25 project-days
etag 1.8.1 PASS All observations passed contract passed 25 project-days
mime-types 3.0.2 PASS All observations passed contract passed 24 project-days
ms 2.1.3 PASS All observations passed contract passed 23 project-days
on-finished 2.4.1 PASS All observations passed contract passed 24 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: 6 · unchanged at every release: 8

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