CodeSampleX

Recordscargosocket20.6.5socket2::Protocol

Change the conditions
Fixed
OSlinux Symbolsocket2::Protocol Package managercargo
Filter Runtimerust 1 Package version0.6.5 Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

socket2::Protocol @0.6.5linux · 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-10-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

0.6.5

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:46e45d8830bc11b4c77917f3bf1bfdd684447a848af8330c8df85f0431fe4501

Library Version Health Measured there Projects
libc 0.2.189 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
libc 0.2.191 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
windows-sys 0.61.2 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.

Moved: 2 · unchanged at every release: 0

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.