CodeSampleX

Recordsgolanggithub.com/json-iterator/gov1.1.12

Change the conditions
Fixed
OSwindows 11 Symbolwhole package Architecturex64
Filter Runtimego 1.26 Package versionv1.1.12 Package managergo 1 Clear filters

Current conditions

github.com/json-iterator/go @v1.1.12windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

25 of 26 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
25 / 26
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Unknown 1 · Steady 1

First observed break

v1.1.12

windows · go@1.26

1 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd CANDIDATE Correlated change; unproven combination builds observed 6 project-days
github.com/modern-go/reflect2 v1.0.2 CANDIDATE Correlated change; unproven combination builds observed 7 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
github.com/stretchr/testify v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/google/gofuzz v1.0.0 UNKNOWN No linked outcome measured nothing measured 6 project-days
github.com/davecgh/go-spew v1.1.1 PASS All observations passed contract passed 7 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