CodeSampleX

Recordscargosynstructure0.13.2synstructure::BindStyle

Change the conditions
Fixed
Symbolsynstructure::BindStyle Package managercargo
Filter OSalpine musl Runtimerust 1 Package version0.13.2 Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

synstructure::BindStyle @0.13.2alpine 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-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

0.13.2

linux

2 FAIL · stage: PROJECT_TEST · fingerprint: sha256:4f232600c5a893bf4f08e6128e9ea91fea9296d2a40a0499ce9057af062e3308

Library Version Health Measured there Projects
syn 2.0.119 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 17 project-days
quote 1.0.47 PASS All observations passed contract passed 17 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: 1 · unchanged at every release: 2

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