CodeSampleX

Recordscargogeneric-array0.14.7generic_array::arr

Change the conditions
Fixed
OSlinux Symbolgeneric_array::arr
Filter Package version0.14.7 Architecturex64 Package managercargo 1 libcglibc Clear filters

Current conditions

generic_array::arr @0.14.7linux · glibc · x64 · cargo 1

5 of 5 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
5 / 5
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-11-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

0.14.7

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:82432d69f18bcc5c068ad19b42779cea4c94019603cf65549bad8147e3d5bf7a

Library Version Health Measured there Projects
typenum 1.20.1 PASS All observations passed contract passed 21 project-days
version_check 0.9.5 PASS All observations passed builds observed 20 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: 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.

Recent failure clusters