CodeSampleX

Recordscargosynstructure0.14.0synstructure

Change the conditions
Fixed
Symbolsynstructure Package managercargo 1
Filter OSubuntu glibc Package version0.14.0 Architecturex64 libcglibc Clear filters

Current conditions

synstructure @0.14.0ubuntu glibc · x64 · cargo 1

0 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
5 / 5
Contract verifications
0 / 3
Independent reporting peers
1
Last recorded
2026-09-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

0.14.0

linux

9 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:b07a18e8da2b85db79ae94f57f091cb6ea8358f16310795caf813cf41867ab8a

Library Version Health Measured there Projects
syn 3.0.6 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
syn 3.0.9 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 70 project-days
quote 1.0.47 PASS All observations passed contract passed 70 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 40 recorded failure clusters. The rest are single reports.