CodeSampleX

Recordsgolanggonum.org/v1/gonum

Change the conditions
Fixed
OSdebian glibc Package versionv0.16.0
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

gonum.org/v1/gonum @v0.16.0debian glibc · x64 · go 1.26 · go · go

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
4 / 4
Contract verifications
1 / 1
Usage records
4
Independent reporting peers
1
Last recorded
2026-09-17

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 4 · Unknown 2 · Steady 2

Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/tools v0.26.0 CHANGED Version changed, no linked failure nothing measured 1 project-day
golang.org/x/tools v0.33.0 CHANGED Version changed, no linked failure nothing measured 3 project-days
golang.org/x/tools v0.34.0 CHANGED Version changed, no linked failure nothing measured 5 project-days
golang.org/x/tools v0.48.0 CHANGED Version changed, no linked failure contract passed 2 project-days
github.com/goccmack/gocc v0.0.0-20230228185258-2292f9e40198 UNKNOWN No linked outcome measured nothing measured 1 project-day
gonum.org/v1/plot v0.15.2 UNKNOWN No linked outcome measured nothing measured 1 project-day
github.com/google/go-cmp v0.6.0 PASS All observations passed contract passed 1 project-day
github.com/google/go-cmp v0.7.0 PASS All observations passed contract passed 10 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: 1 · 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.