CodeSampleX

Recordscargosyn3.0.5

Change the conditions
Fixed
Package version3.0.5 Package managercargo 1
Filter OSubuntu glibc Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

syn @3.0.5ubuntu glibc · x64 · cargo 1

package-level total, not an API

0 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 failed

Project observations
17 / 27
Contract verifications
0 / 1
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

3.0.5

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:4cea358679576b2487958ac4034dc10b763a092bf4d66041d30899a2beb10162

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