CodeSampleX

Recordsnpm@smithy/node-http-handler4.11.3

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

Current conditions

@smithy/node-http-handler @4.11.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 72 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
176 / 208
Contract verifications
0 / 72
Usage records
35
Independent reporting peers
1
Last recorded
2026-10-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

4.11.3

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

11 FAIL · stage: UNKNOWN · fingerprint: sha256:e468cae060059622e4ade91273b8b364e6f61349ef50f7f852d3b6bdb53e21b4

Library Version Health Measured there Projects
@smithy/types 4.17.2 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
@smithy/core 3.33.3 PASS All observations passed contract passed 19 project-days
tslib 2.8.1 PASS All observations passed contract passed 18 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: 1 · 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

Showing the 12 most-reported of 73 recorded failure clusters. The rest are single reports.