Records/cargo/serde_json/1.0.151/axum::body::Body

shared with 6 packages — this evidence cannot say whose API it is

Published samples

• serde_json 1.0.151: Test axum handlers and routing without binding a port by driving the whole Router through tower's ServiceExt::oneshot, and get the exact status for each way a request can be wrong Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtower::ServiceExt::oneshotaxum::Router::routeaxum::Router::with_stateaxum::extract::Pathaxum::extract::Queryaxum::extract::Stateaxum::Jsonaxum::body::Bodyhttp_body_util::BodyExt::collectaxum::debug_handlerrust 1 MIT-0 · 2026-08-14

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-16

Failure clusters

• observed PROJECT_TEST Evidence gap ×2 1.0.149 → 1.0.151 executionContext=rust · os=linux · runtime=rust@1
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-08 · Last seen: 2026-09-08
  Diagnostic re-verification candidate
  Where does this failure start and stop?