CodeSampleX

Recordscargozerocopy-derive0.8.57

Change the conditions
Fixed
Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Package version0.8.57 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

zerocopy-derive @0.8.57ubuntu glibc · x64 · go 1.26 · go 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
2 / 2
Contract verifications
0 / 1
Usage records
5
Independent reporting peers
1
Last recorded
2026-09-20

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

0.8.57

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:32f2fec8d27d12e41f7694913ef1e2d60f9fd8be6b8ac202774bc236b07c58cb

Library Version Health Measured there Projects
proc-macro2 1.0.107 PASS All observations passed contract passed 18 project-days
quote 1.0.47 PASS All observations passed contract passed 18 project-days
syn 2.0.119 PASS All observations passed contract passed 18 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: 0 · unchanged at every release: 3

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