Recordsnpm@aws-sdk/nested-clients
no sample at this coordinate yet
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.997.44
windows · node@24.13 · moduleSystem=esm · executionContext=node
11 FAIL
· stage: UNKNOWN
· fingerprint: sha256:e468cae060059622e4ade91273b8b364e6f61349ef50f7f852d3b6bdb53e21b4
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @aws-sdk/core | 3.977.9 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| @aws-sdk/types | 3.974.5 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| @smithy/core | 3.33.3 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @smithy/fetch-http-handler | 5.7.2 | CANDIDATE Correlated change; unproven combination | contract passed | 18 project-days |
| @smithy/node-http-handler | 4.11.3 | CANDIDATE Correlated change; unproven combination | contract passed | 18 project-days |
| @smithy/types | 4.17.2 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @aws-sdk/signature-v4-multi-region | 3.996.46 | PASS All observations passed | contract passed | 20 project-days |
| tslib | 2.8.1 | PASS All observations passed | contract passed | 19 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: 14 · unchanged at every release: 25
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.