Recordscargoreqwest
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
Showing the environments with the most evidence.
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
0.12.28
linux · rust@1 · executionContext=rust
2 FAIL · stage: PROJECT_TEST
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 | 0.13.4 | 0.12.28 |
|---|---|---|
| base64 | — | 0.22.1 |
| bytes | — | 1.12.1 |
| cookie | — | 0.18.2 |
| cookie_store | — | 0.22.1 |
| futures-core | — | 0.3.34 |
| http | — | 1.5.0 |
| http-body | — | 1.1.0 |
| http-body-util | — | 0.1.5 |
| hyper | — | 1.11.0 |
| hyper-rustls | — | 0.27.9 |
| hyper-util | — | 0.1.20 |
| js-sys | — | 0.3.104 |
| log | — | 0.4.33 |
| percent-encoding | — | 2.3.2 |
| pin-project-lite | — | 0.2.17 |
| quinn | — | 0.11.11 |
| rustls | — | 0.23.43 |
| rustls-pki-types | — | 1.15.1 |
| serde | — | 1.0.229 |
| serde_json | — | 1.0.151 |
| serde_urlencoded | — | 0.7.1 |
| sync_wrapper | — | 1.0.2 |
| tokio | 1.53.1 | 1.53.1 |
| tokio-rustls | — | 0.26.4 |
| tower | — | 0.5.3 |
| tower-http | — | 0.6.11 |
| tower-service | — | 0.3.3 |
| url | — | 2.5.8 |
| wasm-bindgen | — | 0.2.127 |
| wasm-bindgen-futures | — | 0.4.77 |
| web-sys | — | 0.3.104 |
| webpki-roots | — | 1.0.9 |
Moved: 0 · unchanged at every release: 32
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.