CodeSampleX

Recordsgolanggithub.com/json-iterator/gov1.1.11

Change the conditions
Fixed
OSlinux Symbolwhole package Package managergo 1
Filter Runtimego 1.26 Package versionv1.1.11 Architecturex64 libcglibc Clear filters

Current conditions

github.com/json-iterator/go @v1.1.11linux · glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 6 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (13)

Project observations
17 / 18
Contract verifications
0 / 6
Usage records
3
Independent reporting peers
3
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Unknown 1 · Steady 1

First observed break

v1.1.11

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3

Library Version Health Measured there Projects
github.com/modern-go/concurrent v0.0.0-20180228061459-e0a39a4cb421 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd CANDIDATE Correlated change; unproven combination builds observed 14 project-days
github.com/modern-go/reflect2 v0.0.0-20180701023420-4b7aa43c6742 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
github.com/modern-go/reflect2 v1.0.1 CANDIDATE Correlated change; unproven combination nothing measured 14 project-days
github.com/modern-go/reflect2 v1.0.2 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
github.com/stretchr/testify v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
github.com/stretchr/testify v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
github.com/google/gofuzz v1.0.0 UNKNOWN No linked outcome measured nothing measured 27 project-days
github.com/davecgh/go-spew v1.1.1 PASS All observations passed contract passed 27 project-days

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: 3 · unchanged at every release: 2

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.

Recent failure clusters