CodeSampleX

Recordsgolangmodernc.org/mathutilv1.5.0

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

Current conditions

modernc.org/mathutil @v1.5.0ubuntu 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
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Unknown 1 · Steady 1

First observed break

v1.5.0

linux · go@1.26

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/remyoudompheng/bigfft v0.0.0-20200410134404-eec4a21b6bb0 UNKNOWN No linked outcome measured nothing measured 2 project-days
github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec 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.

Libraryv1.7.1v1.5.0
github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec v0.0.0-20230129092748-24d4a6f8daec

Moved: 0 · unchanged at every release: 1

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