CodeSampleX

Recordsgolangmodernc.org/memoryv1.11.0

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

Current conditions

modernc.org/memory @v1.11.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v1.11.0

windows · go@1.26

269 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.46.0 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
golang.org/x/sys v0.47.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
modernc.org/mathutil v1.7.1 CANDIDATE Correlated change; unproven combination contract passed 17 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.12.0v1.11.0v1.5.0
golang.org/x/sys v0.47.0 v0.46.0 —
modernc.org/mathutil v1.7.1 v1.7.1 v1.5.0

Moved: 2 · unchanged at every release: 0

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