Recordsgolanggoogle.golang.org/genprotov0.0.0-20200618031413-b414f8b61790
Change the conditions
Current conditions
google.golang.org/genproto @v0.0.0-20200618031413-b414f8b61790ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 30 / 32
- Contract verifications
- 0 / 3
- Usage records
- 12
- Independent reporting peers
- 1
- Last recorded
- 2026-10-09
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.0-20200618031413-b414f8b61790
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:960c448010d338b23e4225acf905c3ba5fc46c4e38004ca42dccb0ec225d0a82
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.4.2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/lint | v0.0.0-20200302205851-738671d3881b | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/tools | v0.0.0-20200618134242-20370b0cb4b2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/grpc | v1.29.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.24.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| honnef.co/go/tools | v0.0.1-2020.1.4 | 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: 12 · unchanged at every release: 115 Longer lists are cut here; the counts above cover all of them.
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 PROJECT_RESOLVE exit 1 ×2 v0.0.0-20200618031413-b414f8b61790 os=linux · runtime=go@1.26 sha256:960c448010d3…test/contract.go:<n>:<n>: missing go.sum entry for module providing package cloud.google.com/go/storage (imported by example.com/sample/test); to add: …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.0.0-20200618031413-b414f8b61790 os=linux · runtime=go@1.26 sha256:d4de5d3d8f8c…go: downloading cloud.google.com/go/storage v1.10.0 · go: downloading google.golang.org/api v0.28.0 · go: downloading cloud.google.com/go v0.57.0 …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.0.0-20200618031413-b414f8b61790 os=linux · runtime=go@1.26 sha256:ddbc3799877b…FAIL: <token> returned error: storage: expecting Expires to be in the future · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.0.0-20200618031413-b414f8b61790 os=linux · runtime=go@1.26 sha256:e1f54b5fc2bd…FAIL: PostPolicyV4 URL mismatch: got <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19Diagnostic re-verification candidate