Recordscargosynstructure
Change the conditions
Current conditions
synstructure @0.14.0alpine 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
- 8
- Independent reporting peers
- 1
- Last recorded
- 2026-11-06
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
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.