CodeSampleX

Recordsgolanggolang.org/x/oauth2v0.0.0-20210514164344-f6687ab2804c

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

Current conditions

golang.org/x/oauth2 @v0.0.0-20210514164344-f6687ab2804cdebian 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
1
Independent reporting peers
1
Last recorded
2026-09-01

Dependencies

LibraryVersionMeasured thereProjects
cloud.google.com/go v0.65.0 builds observed 1 project-day
golang.org/x/net v0.0.0-20210525063256-abc453219eb5 builds observed 1 project-day

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.0.0-20220223155221-ee480838109bv0.0.0-20210514164344-f6687ab2804c
golang.org/x/net v0.4.0 v0.0.0-20210525063256-abc453219eb5
cloud.google.com/go v0.65.0 v0.65.0
cloud.google.com/go/compute/metadata v0.9.0

Moved: 1 · unchanged at every release: 2

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.