Records/cargo/serde_json/1.0.149/serde_json::Number

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

Published samples

• serde_json 1.0.149: Parsing scientific notation numbers with serde_json arbitrary_precision normalizes positive and uppercase exponents to explicit lowercase e+ formatting matching zmij float serialization starting in 1.0.149 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. HOWserde_json::Numberserde_json::from_strserde_json::to_stringserde_json::Valuerust MIT-0 · 2026-08-16

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-15

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?