CodeSampleX

Recordscargozerocopy0.8.57

Change the conditions
Fixed
Runtimerust 1 Package version0.8.57
Filter OSalpine musl Symbolwhole package Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

zerocopy @0.8.57alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

1 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 came back clean (1)

Project observations
4 / 4
Contract verifications
1 / 1
Usage records
5
Independent reporting peers
1
Last recorded
2026-10-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

0.8.57

linux

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

Library Version Health Measured there Projects
zerocopy-derive 0.8.57 CANDIDATE Correlated change; unproven combination 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.

Library0.8.620.8.570.8.56
zerocopy-derive 0.8.62 0.8.57 0.8.56

Moved: 1 · unchanged at every release: 0

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