CodeSampleX

Recordscargowindows-sys0.61.2windows_sys::Win32::Foundation::FALSE

Change the conditions
Fixed
OSlinux Symbolwindows_sys::Win32::Foundation::FALSE
Filter Package version0.61.2 Architecturex64 Package managercargo 1 libcglibc Clear filters

Current conditions

windows_sys::Win32::Foundation::FALSE @0.61.2linux · glibc · x64 · cargo 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

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

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Steady 1

All 1 dependencies report steady passing evidence.

Library Version Health Measured there Projects
windows-link 0.2.1 PASS All observations passed contract passed 47 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.