Records/golang/github.com/json-iterator/go/v1.1.10/github.com/json-iterator/go.ConfigDefault

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-10-09

Failure clusters

• observed PROJECT_COMPILE exit 1 ×2 v1.1.10 → v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.ConfigDefault sha256:964ddac6b19a…
  <path> <str> imported and not used
  go/compiler · compiler-diagnostic · outer go run, go test
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-19
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v1.1.10 os=linux · runtime=go@1.26 sha256:cb79011d2364…
  panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x40f952] …
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
  Diagnostic re-verification candidate
  Where does this failure start and stop?