CodeSampleX

Recordscargoserde_json

Change the conditions
Fixed
Package version1.0.149
Filter OSalpine musl Runtimerust 1 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

serde_json @1.0.149alpine musl · x64 · rust 1 · cargo · rust

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations
2 / 3
Contract verifications
1 / 2
Usage records
3
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 5

First observed break

1.0.149

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 1 project-day
memchr 2.8.3 PASS All observations passed contract passed 1 project-day
serde 1.0.229 PASS All observations passed contract passed 1 project-day
serde_core 1.0.229 PASS All observations passed contract passed 1 project-day
zmij 1.0.23 PASS All observations passed contract passed 1 project-day

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.