CodeSampleX

Recordsgolangmodernc.org/sqlitev1.56.0

Change the conditions
Fixed
OSalpine musl Package versionv1.56.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

modernc.org/sqlite @v1.56.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

19 of 27 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (16)

Project observations
12 / 13
Contract verifications
19 / 27
Usage records
7
Independent reporting peers
2
Failures with a captured fingerprint
0 / 1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

v1.56.0

go@1.26

271 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/google/pprof v0.0.0-20260802141513-ef3492d7dac3 CANDIDATE Correlated change; unproven combination nothing measured 14 project-days
golang.org/x/sys v0.47.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
modernc.org/libc v1.74.4 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
modernc.org/libc v1.75.3 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
modernc.org/mathutil v1.7.1 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
modernc.org/fileutil v1.4.0 PASS All observations passed contract passed 14 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.

Libraryv1.56.0v1.23.1
github.com/google/pprof v0.0.0-20260802141513-ef3492d7dac3 v0.0.0-20221118152302-e6195bd50e26
golang.org/x/sys v0.47.0 v0.7.0
modernc.org/libc v1.75.3 v1.22.5
modernc.org/mathutil v1.7.1 v1.5.0
github.com/klauspost/cpuid/v2 — v2.2.3
github.com/mattn/go-sqlite3 — v1.14.16
modernc.org/ccgo/v3 — v3.16.13
modernc.org/fileutil v1.4.0 —
modernc.org/tcl — v1.15.2

Moved: 4 · unchanged at every release: 5

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