CodeSampleX

Recordscargowindows-sys

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

Current conditions

windows-sys @0.48.0alpine musl · x64 · rust 1 · cargo · rust

2 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 came back clean (2)

Project observations
2 / 2
Contract verifications
2 / 2
Usage records
2
Independent reporting peers
1
Last recorded
2026-10-22

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

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

Library Version Health Measured there Projects
windows-targets 0.48.5 CHANGED Version changed, no linked failure contract passed 5 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.