Recordscargowindows-sys
Change the conditions
Current conditions
windows-sys @0.52.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
- 4 / 4
- Contract verifications
- 2 / 2
- Usage records
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
windows_sys
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.52.0
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:3bab2c36697ae87f0083cdff268e736f69095a01fcc4e102864fa4f14bf20993
| 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.
| Library | 0.61.2 | 0.52.0 | 0.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.