CodeSampleX

Recordsgolangmodernc.org/sqlitev1.23.1

Change the conditions
Fixed
OSubuntu glibc Package versionv1.23.1
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

modernc.org/sqlite @v1.23.1ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

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 (1)

Project observations
4 / 4
Contract verifications
0 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

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

First observed break

v1.23.1

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:5299cca1c440bf07bc38e84fef5b85ae3213905355fe5dd433e106a2ba76d8a5

Library Version Health Measured there Projects
github.com/google/pprof v0.0.0-20221118152302-e6195bd50e26 CANDIDATE Correlated change; unproven combination nothing measured 2 project-days
golang.org/x/sys v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
modernc.org/libc v1.22.5 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
modernc.org/mathutil v1.5.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/klauspost/cpuid/v2 v2.2.3 UNKNOWN No linked outcome measured nothing measured 2 project-days
github.com/mattn/go-sqlite3 v1.14.16 UNKNOWN No linked outcome measured nothing measured 2 project-days
modernc.org/ccgo/v3 v3.16.13 UNKNOWN No linked outcome measured nothing measured 2 project-days
modernc.org/tcl v1.15.2 UNKNOWN No linked outcome measured nothing measured 2 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: 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