CodeSampleX

Recordscargosyn

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

Current conditions

syn @3.0.6ubuntu glibc · x64 · cargo 1

0 of 11 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
165 / 241
Contract verifications
0 / 11
Usage records
11
Independent reporting peers
1
Last recorded
2026-10-09

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:0479254218ac3780b34745e946705b5f6ea072bc45cc7771f5a9b6fbfb5955e8

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.