CodeSampleX

Recordscargowindows-sys0.52.0windows_sys

Change the conditions
Fixed
OSalpine musl Symbolwindows_sys
Filter Runtimerust 1 Package version0.52.0 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

windows_sys @0.52.0alpine musl · x64 · rust 1 · cargo · rust

1 of 1 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

0.52.0

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:3bab2c36697ae87f0083cdff268e736f69095a01fcc4e102864fa4f14bf20993

View exact conditions View failure cluster
Library Version Health Measured there Projects
windows-targets 0.52.6 CANDIDATE Correlated change; unproven combination contract passed 23 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.

Library0.61.20.52.00.48.0
windows-targets — 0.52.6 0.48.5
windows-link 0.2.1 — —

Moved: 1 · 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