CodeSampleX

Recordsgolanggithub.com/google/s2a-gov0.1.9

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

Current conditions

github.com/google/s2a-go @v0.1.9alpine 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-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 2

First observed break

v0.1.9

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/crypto v0.52.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.81.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/sync v0.20.0 PASS All observations passed contract passed 2 project-days
google.golang.org/api v0.277.0 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.

Libraryv0.1.9v0.1.7
github.com/google/go-cmp v0.7.0 v0.6.0
golang.org/x/crypto v0.52.0 v0.22.0
google.golang.org/grpc v1.81.0 v1.67.1
google.golang.org/protobuf v1.36.11 v1.35.1
github.com/golang/protobuf — v1.5.4
golang.org/x/sync v0.20.0 —
google.golang.org/api v0.277.0 —

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.

Recent failure clusters