CodeSampleX

Recordsnpmsend0.18.0

Change the conditions
Fixed
Package version0.18.0 Package managernpm 11
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

send @0.18.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

2 of 2 passed

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
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 7

First observed break

0.18.0

executionContext=node

16 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
debug 2.6.9 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
encodeurl 1.0.2 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
fresh 0.5.2 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
http-errors 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
range-parser 1.2.1 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
statuses 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
depd 2.0.0 PASS All observations passed contract passed 9 project-days
destroy 1.2.0 PASS All observations passed contract passed 9 project-days
escape-html 1.0.3 PASS All observations passed contract passed 9 project-days
etag 1.8.1 PASS All observations passed contract passed 9 project-days
mime 1.6.0 PASS All observations passed contract passed 5 project-days
ms 2.1.3 PASS All observations passed contract passed 7 project-days
on-finished 2.4.1 PASS All observations passed contract passed 7 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.

Library1.2.10.19.20.19.00.18.0
debug 4.4.3 2.6.9 2.6.9 2.6.9
encodeurl 2.0.0 2.0.0 1.0.2 1.0.2
fresh 2.0.0 0.5.2 0.5.2 0.5.2
http-errors 2.0.1 2.0.1 2.0.0 2.0.0
range-parser 1.3.0 1.2.1 1.2.1 1.2.1
statuses 2.0.2 2.0.2 2.0.1 2.0.1
depd — 2.0.0 2.0.0 2.0.0
destroy — 1.2.0 1.2.0 1.2.0
escape-html 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
mime — 1.6.0 1.6.0 1.6.0
mime-types 3.0.2 — — —
ms 2.1.3 2.1.3 2.1.3 2.1.3
on-finished 2.4.1 2.4.1 2.4.1 2.4.1

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