CodeSampleX

Recordscargosyn2.0.119syn

Change the conditions
Fixed
Package version2.0.119 Symbolsyn Package managercargo
Filter OSalpine musl Runtimerust 1 Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

syn @2.0.119alpine 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 4 · Steady 2

First observed break

2.0.119

linux

10 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:4c786cbbce8a4d62372582ec22f7ee5dde092da981551c703d9b07deb35c9524

Library Version Health Measured there Projects
unicode-ident 1.0.24 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
unicode-ident 1.0.25 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
unicode-ident 1.0.26 CANDIDATE Correlated change; unproven combination contract passed 47 project-days
unicode-ident 1.0.27 CANDIDATE Correlated change; unproven combination contract passed 78 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 151 project-days
quote 1.0.47 PASS All observations passed contract passed 151 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

Showing the 12 most-reported of 100 recorded failure clusters. The rest are single reports.