CodeSampleX

Recordsgolanggithub.com/google/s2a-gov0.1.7

Change the conditions
Fixed
OSalpine musl Package versionv0.1.7
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

github.com/google/s2a-go @v0.1.7alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Changed 6 · Steady 1

Dependency changes observed: 6. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/google/go-cmp v0.6.0 CHANGED Version changed, no linked failure contract passed 2 project-days
golang.org/x/crypto v0.22.0 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/grpc v1.63.2 CHANGED Version changed, no linked failure builds observed 1 project-day
google.golang.org/grpc v1.67.1 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.33.0 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.35.1 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/golang/protobuf v1.5.4 PASS All observations passed 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.

Moved: 4 · unchanged at every release: 3

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.