CodeSampleX

Recordsgolanggoogle.golang.org/protobufv1.36.10google.golang.org/protobuf/encoding/protojson.MarshalOptions

Change the conditions
Fixed
Package versionv1.36.10 Symbolgoogle.golang.org/protobuf/encoding/protojson.MarshalOptions
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

google.golang.org/protobuf/encoding/protojson.MarshalOptions @v1.36.10ubuntu glibc · x64 · go 1.26 · go 1

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 (1)

Project observations
6 / 7
Contract verifications
0 / 3
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 2 · Steady 0

First observed break

v1.36.10 github.com/golang/protobuf@v1.5.0

go@1.26

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/golang/protobuf v1.5.0 FAIL Linked failure observed; version changed across releases contract passed 2 project-days
github.com/google/go-cmp v0.7.0 FAIL Linked failure observed; version changed across releases contract passed 2 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.

Libraryv1.36.12v1.36.11v1.36.10v1.36.6v1.36.5v1.34.2v1.33.0v1.32.0v1.28.0v1.26.0v1.26.0-rc.1
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 —
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

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.

Recent failure clusters