CodeSampleX

Recordscargoserde_json1.0.151

Change the conditions
Fixed
Package version1.0.151 Symbolwhole package Package managercargo 1
Filter OSubuntu glibc Architecturex64 libcglibc Clear filters

Current conditions

serde_json @1.0.151ubuntu glibc · x64 · cargo 1

package-level total, not an API

7 of 7 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (12)

Project observations
7 / 7
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 5

First observed break

1.0.151

linux · rust@1 · executionContext=rust

2 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
itoa 1.0.18 PASS All observations passed contract passed 25 project-days
memchr 2.8.3 PASS All observations passed contract passed 25 project-days
serde 1.0.229 PASS All observations passed contract passed 25 project-days
serde_core 1.0.229 PASS All observations passed contract passed 25 project-days
zmij 1.0.23 PASS All observations passed contract passed 25 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: 5

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