Recordsgolanggolang.org/x/oauth2
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
Showing the environments with the most evidence.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.36.0
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:dda800f87ad336ceb3470d5a3d62662cd8dbf7f91f2b28e427be0c6fc592b4b7
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.
| Library | v0.36.0 | v0.22.0 | v0.19.0 | v0.0.0-20220223155221-ee480838109b | v0.0.0-20210514164344-f6687ab2804c | v0.0.0-20200107190931-bf48bf16ab8d | v0.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.