CodeSampleX

Recordsgolanggolang.org/x/oauth2v0.0.0-20190226205417-e64efc72b421

Change the conditions
Fixed
OSdebian glibc Package versionv0.0.0-20190226205417-e64efc72b421
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/oauth2 @v0.0.0-20190226205417-e64efc72b421debian glibc · 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
4
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v0.0.0-20190226205417-e64efc72b421

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:0cc5633d6f9aa11fdb97a30243cae2d23c42f9bbcc21f59ae64b43eea06d4a3e

View exact conditions View failure cluster
Library Version Health Measured there Projects
cloud.google.com/go v0.34.0 CANDIDATE Correlated change; unproven combination nothing measured 16 project-days
cloud.google.com/go v0.37.0 CANDIDATE Correlated change; unproven combination builds observed 5 project-days
golang.org/x/net v0.0.0-20190313220215-9f648a60d977 CANDIDATE Correlated change; unproven combination builds observed 4 project-days
golang.org/x/net v0.0.0-20200625001655-4c5254603344 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
google.golang.org/appengine v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 19 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.36.0v0.22.0v0.19.0v0.0.0-20220223155221-ee480838109bv0.0.0-20210514164344-f6687ab2804cv0.0.0-20200107190931-bf48bf16ab8dv0.0.0-20190226205417-e64efc72b421
cloud.google.com/go — — — v0.65.0 v0.65.0 v0.65.0 v0.37.0
cloud.google.com/go/compute/metadata v0.9.0 v0.5.0 v0.3.0 — — — —
golang.org/x/net — — — v0.4.0 v0.0.0-20210525063256-abc453219eb5 v0.0.0-20200822124328-c89045814202 v0.0.0-20190313220215-9f648a60d977
google.golang.org/appengine — — — — v1.6.6 v1.6.5 v1.4.0
github.com/google/go-cmp — v0.6.0 v0.6.0 — — — —

Moved: 4 · unchanged at every release: 1

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