Recordsgolanggolang.org/x/modv0.41.0
Change the conditions
Current conditions
golang.org/x/mod @v0.41.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-10-19
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.41.0
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:825e05b09b71b3ddf79a1fbdc411ca159ac894d60360e31a63931e29d4938da6
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.50.0 | CANDIDATE Correlated change; unproven combination | 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.
Moved: 3 · unchanged at every release: 0
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
-
observed UNKNOWN exit 1 ERROR Evidence gap ×2 v0.41.0 os=linux · runtime=go@1.26 sha256:825e05b09b71…verifying modernc.org/mathutil@v1.6.0/go.mod: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token> · SECURITY ERRORgo · unclassified-diagnostic · outer go mod · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate