Recordsgolanggolang.org/x/modv0.2.0
Change the conditions
Current conditions
golang.org/x/mod @v0.2.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
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-11-04
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.2.0
linux · go@1.26
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0882784d80c20e919569b4a9a1a5ff54eb0aa7665750aedc7afd0bce723472f8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.0.0-20191011191535-87dc89f01550 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| golang.org/x/tools | v0.0.0-20200204074204-1cc6d1ef6c74 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/tools | v0.0.0-20200212150539-ea181f53ac56 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/tools | v0.0.0-20200224181240-023911ca70b2 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/tools | v0.0.0-20200331025713-a30bf2db82d4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/xerrors | v0.0.0-20191204190536-9bdfabe68543 | CANDIDATE Correlated change; unproven combination | contract passed | 13 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.
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 Evidence gap ×3 v0.1.1-0.20191107180719-034126e5016b → v0.2.0 → v0.4.2 os=linux · runtime=go@1.26 sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-23Diagnostic re-verification candidate