Recordsgolanggithub.com/spf13/cast
Change the conditions
Current conditions
github.com/spf13/cast @v1.3.1debian glibc · x64 · go 1.26 · go · go
2 of 2 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 (2)
- Project observations
- 8 / 8
- Contract verifications
- 2 / 2
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-10-10
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
github.com/spf13/cast.ToBool
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.3.1
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:42e7b5ec841f4c528f55b90c6316b7ba0a100cc0de5f2e3c81a30dc9db854770
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.2.2 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| github.com/stretchr/testify | v1.5.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 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.
| Library | v1.10.0 | v1.7.0 | v1.4.1 | v1.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.