CodeSampleX

Recordscargocc1.4.3

Change the conditions
Fixed
Package version1.4.3 Architecturex64
Filter OSalpine musl Runtimerust 1 Symbolwhole package Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

cc @1.4.3alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Unknown 1 · Steady 2

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
find-msvc-tools 0.1.11 CHANGED Version changed, no linked failure nothing measured 9 project-days
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 12 project-days
jobserver 0.1.35 PASS All observations passed builds observed 2 project-days
libc 0.2.189 PASS All observations passed contract passed 2 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: 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.