Recordsgolanggithub.com/rogpeppe/go-internalv1.3.0github.com/rogpeppe/go-internal/semver.IsValid
Change the conditions
Current conditions
github.com/rogpeppe/go-internal/semver.IsValid @v1.3.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
Dependency Health
Observed combinations and failure evidence for this release
All 1 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| gopkg.in/errgo.v2 | v2.1.0 | PASS All observations passed | contract passed | 36 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.9.0 | v1.3.0 |
|---|---|---|
| github.com/pkg/diff | v0.0.0-20210226163009-20ebb0f2a09e | — |
| gopkg.in/errgo.v2 | — | v2.1.0 |
Moved: 0 · unchanged at every release: 2
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.