Recordsgolanggithub.com/json-iterator/gov1.1.11
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
3 5○ 12026-09-17
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
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.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 5✓ — Verified: CONTRACT 13✓
|
LOW | 8 +5 | 13 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 1✓ 1✕ · PROJECT_PROCESS 15✓ · PROJECT_TEST 1✓ — Usage: USED 3✓ — Verified: UNKNOWN 0✓ 6✕
|
ELEVATED FAILURE | 18 +3 | 6 | 71% | 3 | 2026-09-05 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v1.1.11 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.Marshal sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary sha256:58bc61b551cd…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-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary sha256:61947629f29b…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-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.Marshal sha256:762c4b527147…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x40f992] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.Config sha256:a9f8c7e0c673…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x1d pc=0x40f952] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.11 os=linux · runtime=go@1.26 github.com/json-iterator/go.ConfigDefault sha256:cad8582842d4…signal: killedgo · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05Diagnostic re-verification candidate
Symbols
- github.com/json-iterator/go.Any
- github.com/json-iterator/go.ArrayValue
- github.com/json-iterator/go.BoolValue
- jsoniter.Config 1
- github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary 1 1 of 3 runs passed
- github.com/json-iterator/go.ConfigDefault 0 of 1 runs passed
- github.com/json-iterator/go.Get 1 1 of 2 runs passed
- github.com/json-iterator/go.InvalidValue
- github.com/json-iterator/go.Iterator
- github.com/json-iterator/go.Marshal 2
- jsoniter.NewIterator 1
- jsoniter.NewStream 2
- github.com/json-iterator/go.NilValue
- github.com/json-iterator/go.NumberValue
- github.com/json-iterator/go.ObjectValue
- jsoniter.Parse 2
- jsoniter.ParseBytes 1
- github.com/json-iterator/go.Stream
- github.com/json-iterator/go.StringValue
- jsoniter.Unmarshal 1
- github.com/json-iterator/go.ValueType
Published samples
- github.com/json-iterator/go v1.1.11 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. HOW MIT-0 · 2026-09-04