CodeSampleX

Recordsgolanggithub.com/spf13/castv1.10.0cast.ToBoolE

Change the conditions
Fixed
OSdebian glibc Symbolcast.ToBoolE
Filter Runtimego 1.26 Package versionv1.10.0 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

cast.ToBoolE @v1.10.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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
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