CodeSampleX

Recordsgolanggoogle.golang.org/protobufv1.28.0google.golang.org/protobuf/types/known/structpb.NewStruct

Change the conditions
Fixed
Package versionv1.28.0 Symbolgoogle.golang.org/protobuf/types/known/structpb.NewStruct
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

google.golang.org/protobuf/types/known/structpb.NewStruct @v1.28.0debian glibc · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-09-02

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 2 · Steady 0

First observed break

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

linux · node@22.23 · executionContext=node

15 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

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

Recent failure clusters