CodeSampleX

Recordscargosyn

Change the conditions
Fixed
Package version3.0.6 Package managercargo
Filter OSalpine musl Runtimerust 1 Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

syn @3.0.6alpine 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
5
Independent reporting peers
1
Last recorded
2026-10-13

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

3.0.6

linux

5 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:113664d7d9181e86107a4fb50e44d53895730e410223b707c0b72d659b247aef

Library Version Health Measured there Projects
unicode-ident 1.0.25 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
unicode-ident 1.0.26 CANDIDATE Correlated change; unproven combination contract passed 87 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 107 project-days
quote 1.0.47 PASS All observations passed contract passed 107 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.