Recordsnpm@aws-sdk/token-providers
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 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.
| Library | 3.1116.0 | 3.975.0 | 3.958.0 |
|---|---|---|---|
| @aws-sdk/core | 3.977.9 | 3.973.3 | 3.957.0 |
| @aws-sdk/nested-clients | 3.997.44 | 3.975.0 | 3.958.0 |
| @aws-sdk/types | 3.974.5 | 3.973.1 | 3.957.0 |
| @smithy/types | 4.17.2 | 4.12.0 | 4.12.0 |
| @smithy/core | 3.33.3 | — | — |
| @smithy/property-provider | — | 4.2.8 | 4.2.8 |
| @smithy/shared-ini-file-loader | — | 4.4.3 | 4.4.3 |
| tslib | 2.8.1 | 2.8.1 | 2.8.1 |
Moved: 4 · unchanged at every release: 4
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.