CodeSampleX

Recordscargocrypto-common0.1.7

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

Current conditions

crypto-common @0.1.7alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
2
Last recorded
2026-11-04

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

0.1.7

linux

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

Library Version Health Measured there Projects
generic-array 0.14.7 PASS All observations passed contract passed 13 project-days
typenum 1.20.1 PASS All observations passed contract passed 13 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.2.20.1.7
generic-array — 0.14.7
hybrid-array 0.4.15 —
typenum — 1.20.1

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