CodeSampleX

Recordsgolanggorm.io/gormv1.31.2DB.Create

Change the conditions
Fixed
SymbolDB.Create
Filter OSalpine musl Runtimego 1.26 Package versionv1.31.2 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

DB.Create @v1.31.2alpine musl · x64 · go 1.26 · go · go

5 of 7 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 (3)

Project observations
nothing at this coordinate
Contract verifications
5 / 7
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

v1.31.2

linux · go@1.26 · executionContext=go

2 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/jinzhu/inflection v1.0.0 PASS All observations passed contract passed 2 project-days
github.com/jinzhu/now v1.1.5 PASS All observations passed contract passed 2 project-days
golang.org/x/text v0.20.0 PASS All observations passed contract passed 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: 0 · unchanged at every release: 3

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