CodeSampleX

Recordsnpm@aws-sdk/client-rekognition3.1121.0

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

Current conditions

@aws-sdk/client-rekognition @3.1121.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

7 of 9 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependencies

LibraryVersionMeasured thereProjects
@aws-sdk/core 3.977.9 contract passed 2 project-days
@aws-sdk/credential-provider-node 3.972.81 contract passed 2 project-days
@aws-sdk/types 3.974.5 contract passed 2 project-days
@smithy/core 3.33.3 contract passed 2 project-days
@smithy/fetch-http-handler 5.7.2 contract passed 2 project-days
@smithy/node-http-handler 4.11.3 contract passed 2 project-days
@smithy/types 4.17.2 contract passed 2 project-days
tslib 2.8.1 contract passed 1 project-day

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.1121.03.958.0
@aws-sdk/core 3.977.9 3.957.0
@aws-sdk/credential-provider-node 3.972.81 3.958.0
@aws-sdk/types 3.974.5 3.957.0
@smithy/core 3.33.3 3.22.0
@smithy/fetch-http-handler 5.7.2 5.3.9
@smithy/node-http-handler 4.11.3 4.4.8
@smithy/types 4.17.2 4.12.0
@aws-crypto/sha256-browser — 5.2.0
@aws-crypto/sha256-js — 5.2.0
@aws-sdk/middleware-host-header — 3.957.0
@aws-sdk/middleware-logger — 3.957.0
@aws-sdk/middleware-recursion-detection — 3.957.0
@aws-sdk/middleware-user-agent — 3.957.0
@aws-sdk/region-config-resolver — 3.957.0
@aws-sdk/util-endpoints — 3.957.0
@aws-sdk/util-user-agent-browser — 3.957.0
@aws-sdk/util-user-agent-node — 3.957.0
@smithy/config-resolver — 4.4.6
@smithy/hash-node — 4.2.8
@smithy/invalid-dependency — 4.2.8
@smithy/middleware-content-length — 4.2.8
@smithy/middleware-endpoint — 4.4.12
@smithy/middleware-retry — 4.4.29
@smithy/middleware-serde — 4.2.9
@smithy/middleware-stack — 4.2.8
@smithy/node-config-provider — 4.3.8
@smithy/protocol-http — 5.3.8
@smithy/smithy-client — 4.11.1
@smithy/url-parser — 4.2.8
@smithy/util-base64 — 4.3.0
@smithy/util-body-length-browser — 4.2.0
@smithy/util-body-length-node — 4.2.1
@smithy/util-defaults-mode-browser — 4.3.28
@smithy/util-defaults-mode-node — 4.2.31
@smithy/util-endpoints — 3.2.8
@smithy/util-middleware — 4.2.8
@smithy/util-retry — 4.2.8
@smithy/util-utf8 — 4.2.0
@smithy/util-waiter — 4.2.8
tslib 2.8.1 2.8.1

Moved: 7 · unchanged at every release: 33

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