CodeSampleX

Recordscargozerofrom-derive

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

Current conditions

zerofrom-derive @0.1.7ubuntu glibc · x64 · cargo 1

7 of 8 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
7 / 8
Contract verifications
nothing at this coordinate
Usage records
1
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.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

0.1.7

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:6ab2a1478c5d4ce9298925781b634f0a9fe0d9e9e43074177dc2abdb4d70be83

Library Version Health Measured there Projects
syn 2.0.119 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
synstructure 0.13.2 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 9 project-days
quote 1.0.47 PASS All observations passed contract passed 9 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: 2 · 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.