CodeSampleX

Recordscargowindows-targets0.52.6

Change the conditions
Fixed
OSlinux Package version0.52.6 Package managercargo 1
Filter Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

windows-targets @0.52.6linux · glibc · x64 · cargo 1

package-level total, not an API

0 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
20 / 33
Contract verifications
0 / 2
Usage records
1
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 1

First observed break

0.52.6

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:581c58c1c7ac1c174300ebe7fe6f6efcea19fe2db06561b3fdd49b3747eccc95

Library Version Health Measured there Projects
windows_aarch64_gnullvm 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_aarch64_msvc 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_i686_gnu 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_i686_msvc 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_x86_64_gnu 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_x86_64_gnullvm 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_x86_64_msvc 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
windows_i686_gnullvm 0.52.6 PASS All observations passed contract passed 28 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: 7 · unchanged at every release: 1

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.

Recent failure clusters

Showing the 12 most-reported of 14 recorded failure clusters. The rest are single reports.