Recordscargosyn2.0.119syn
Change the conditions
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
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| unicode-ident | 1.0.24 | CHANGED Version changed, no linked failure | contract passed | 20 project-days |
| unicode-ident | 1.0.25 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| unicode-ident | 1.0.26 | CHANGED Version changed, no linked failure | contract passed | 35 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 | 61 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.
| Library | 3.0.6 | 3.0.5 | 3.0.3 | 2.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.