Recordscargocc
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| find-msvc-tools | 0.1.12 | CHANGED Version changed, no linked failure | nothing measured | 3 project-days |
| shlex | 2.0.1 | UNKNOWN No linked outcome measured | nothing measured | 3 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.
| Library | 1.4.7 | 1.4.6 | 1.4.3 | 1.4.0 |
|---|---|---|---|---|
| find-msvc-tools | 0.1.13 | 0.1.12 | 0.1.12 | 0.1.9 |
| jobserver | — | — | 0.1.35 | 0.1.35 |
| libc | — | — | 0.2.189 | 0.2.189 |
| shlex | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 |
Moved: 1 · unchanged at every release: 3
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.