CodeSampleX

Recordsgolanggithub.com/spf13/castv1.10.0github.com/spf13/cast.ToBool

Change the conditions
Fixed
OSlinux Package versionv1.10.0 Symbolgithub.com/spf13/cast.ToBool
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/spf13/cast.ToBool @v1.10.0linux · glibc · x64 · go 1.26 · go 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-06
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

v1.10.0

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:505fcd91bbc7ae091d2c7fe05998fe8c21822c1a66c7a729492f91f209a80aa6

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/frankban/quicktest v1.14.6 PASS All observations passed contract passed 12 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.10.0v1.7.0v1.4.1v1.3.1
github.com/stretchr/testify — — v1.9.0 v1.2.2
github.com/frankban/quicktest v1.14.6 v1.14.6 — —

Moved: 1 · 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