Recordsgolanggoogle.golang.org/protobuf
Change the conditions
Current conditions
google.golang.org/protobuf/types/known/structpb.NewStruct @v1.36.12x64 · go 1.26 · go
1 of 2 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
- Project observations
- 5 / 6
- Contract verifications
- 1 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
0 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.36.12
linux · node@22.23 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 33 project-days |
| github.com/golang/protobuf | v1.5.2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 43 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.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 | v1.34.2 | v1.33.0 | v1.32.0 | v1.28.0 | v1.26.0 | v1.26.0-rc.1 | v1.23.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.0 | v1.5.0 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.0 | v1.5.3 | — | v1.4.3 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.4.0 |
Moved: 2 · 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.