Recordsgolanggoogle.golang.org/grpcv1.67.1
Change the conditions
Current conditions
google.golang.org/grpc @v1.67.1alpine musl · x64 · go 1.26 · go · go
package-level total, not an API
2 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (2)
- Project observations
- 4 / 5
- Contract verifications
- 2 / 4
- Usage records
- 5
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.67.1
linux · go@1.26
5 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cespare/xxhash/v2 | v2.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/cncf/xds/go | v0.0.0-20240723142845-024c85f92f20 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| github.com/envoyproxy/go-control-plane | v0.13.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| github.com/golang/glog | v1.2.2 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/google/uuid | v1.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.28.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/net | v0.38.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/oauth2 | v0.22.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/sync | v0.8.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| golang.org/x/sys | v0.24.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| golang.org/x/sys | v0.31.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20240814211410-ddb44dafa142 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20241007155032-5fefd90f89a9 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.34.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| google.golang.org/protobuf | v1.35.1 | 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: 27 · unchanged at every release: 5
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_TEST Evidence gap ×5 v1.58.1 → v1.67.1 → v1.71.0 → v1.83.0 os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-26 · Last seen: 2026-09-08Diagnostic re-verification candidate