CodeSampleX

Recordscargoicu_provider2.3.0

Change the conditions
Fixed
OSlinux Package version2.3.0 Package managercargo
Filter Runtimerust 1 Symbolwhole package Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

icu_provider @2.3.0linux · 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
2 / 2
Contract verifications
1 / 1
Usage records
3
Independent reporting peers
1
Last recorded
2026-10-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 8

First observed break

2.3.0

linux

5 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:113664d7d9181e86107a4fb50e44d53895730e410223b707c0b72d659b247aef

Library Version Health Measured there Projects
zerovec 0.11.7 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
zerovec 0.11.8 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
displaydoc 0.2.7 PASS All observations passed contract passed 9 project-days
icu_locale_core 2.3.0 PASS All observations passed contract passed 9 project-days
serde 1.0.229 PASS All observations passed contract passed 5 project-days
stable_deref_trait 1.2.1 PASS All observations passed contract passed 5 project-days
writeable 0.6.4 PASS All observations passed contract passed 9 project-days
yoke 0.8.3 PASS All observations passed contract passed 8 project-days
zerofrom 0.1.8 PASS All observations passed contract passed 9 project-days
zerotrie 0.2.5 PASS All observations passed contract passed 9 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: 8

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