Recordsgolanggithub.com/json-iterator/gov1.1.10github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary
Change the conditions
Current conditions
github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary @v1.1.10ubuntu glibc · x64 · go 1.26 · go 1
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- nothing at this coordinate
- Contract verifications
- 0 / 1
- Last recorded
- 2026-09-19
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.1.10
linux · go@1.26
2 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 | 1 project-day |
| github.com/modern-go/concurrent | v0.0.0-20180306012644-bacd9c7ef1dd | CANDIDATE Correlated change; unproven combination | builds observed | 5 project-days |
| github.com/modern-go/reflect2 | v0.0.0-20180701023420-4b7aa43c6742 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/modern-go/reflect2 | v1.0.1 | CANDIDATE Correlated change; unproven combination | nothing measured | 5 project-days |
| github.com/stretchr/testify | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/stretchr/testify | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| 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 | 6 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
-
observed PROJECT_COMPILE exit 1 ×2 v1.1.10 → v1.1.11 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go run, go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-19
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.1.10 os=linux · runtime=go@1.26 github.com/json-iterator/go.ConfigCompatibleWithStandardLibrary 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-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate