CodeSampleX

Recordscargosyn3.0.3syn::ExprIf

Change the conditions
Fixed
OSalpine musl Package version3.0.3 Symbolsyn::ExprIf
Filter Runtimerust 1 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

syn::ExprIf @3.0.3alpine 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 2

First observed break

3.0.3

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:120b2f5dde9fce592cd7cfeecb9fd13b68fc9e8d3e35ed9c074c0c7cbc3829a6

View exact conditions View failure cluster
Library Version Health Measured there Projects
unicode-ident 1.0.24 CANDIDATE Correlated change; unproven combination contract passed 43 project-days
unicode-ident 1.0.25 CANDIDATE Correlated change; unproven combination builds observed 11 project-days
unicode-ident 1.0.26 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 61 project-days
quote 1.0.47 PASS All observations passed contract passed 60 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.

Library3.0.63.0.53.0.32.0.119
unicode-ident 1.0.25 1.0.25 1.0.26 1.0.25
proc-macro2 1.0.107 1.0.107 1.0.107 1.0.107
quote 1.0.47 1.0.47 1.0.47 1.0.47

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