CodeSampleX

Recordscargozerovec0.11.8

Change the conditions
Fixed
OSlinux Package version0.11.8 Package managercargo 1
Filter Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

zerovec @0.11.8linux · glibc · x64 · cargo 1

package-level total, not an API

0 of 4 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
123 / 173
Contract verifications
0 / 4
Usage records
12
Independent reporting peers
1
Last recorded
2026-10-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

0.11.8

linux

9 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:b07a18e8da2b85db79ae94f57f091cb6ea8358f16310795caf813cf41867ab8a

Library Version Health Measured there Projects
zerovec-derive 0.11.6 CANDIDATE Correlated change; unproven combination contract passed 63 project-days
serde 1.0.229 PASS All observations passed contract passed 30 project-days
yoke 0.8.3 PASS All observations passed contract passed 57 project-days
zerofrom 0.1.8 PASS All observations passed contract passed 83 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: 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

Showing the 12 most-reported of 35 recorded failure clusters. The rest are single reports.