Recordsgolanggithub.com/stretchr/testifyv1.4.0
Change the conditions
Current conditions
github.com/stretchr/testify @v1.4.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.1 | contract passed | 1 project-day |
| github.com/pmezard/go-difflib | v1.0.0 | contract passed | 1 project-day |
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.11.1 | v1.8.1 | v1.4.0 |
|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.1 | v1.1.1 | v1.1.1 |
| github.com/pmezard/go-difflib | v1.0.0 | v1.0.0 | v1.0.0 |
| github.com/stretchr/objx | v0.1.0 | — | — |
| gopkg.in/yaml.v3 | v3.0.1 | v3.0.1 | — |
Moved: 0 · unchanged at every release: 4
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.