Recordsgolanggoogle.golang.org/apiv0.1.0
Change the conditions
Current conditions
google.golang.org/api @v0.1.0debian 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.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 15. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.2.0 | CHANGED Version changed, no linked failure | nothing measured | 7 project-days |
| github.com/google/go-cmp | v0.6.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/oauth2 | v0.0.0-20181203162652-d668ce993890 | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/oauth2 | v0.0.0-20190226205417-e64efc72b421 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| golang.org/x/oauth2 | v0.16.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| golang.org/x/sync | v0.0.0-20181108010431-42b317875d0f | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| golang.org/x/sync | v0.0.0-20190227155943-e225da77a7e6 | CHANGED Version changed, no linked failure | nothing measured | 6 project-days |
| golang.org/x/sync | v0.12.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/appengine | v1.3.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| google.golang.org/appengine | v1.4.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| google.golang.org/genproto | v0.0.0-20181202183823-bd91e49a0898 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| google.golang.org/genproto | v0.0.0-20190306203927-b5d61aea6440 | CHANGED Version changed, no linked failure | builds observed | 7 project-days |
| google.golang.org/grpc | v1.17.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| google.golang.org/grpc | v1.19.0 | CHANGED Version changed, no linked failure | builds observed | 6 project-days |
| google.golang.org/grpc | v1.67.1 | CHANGED Version changed, no linked failure | contract passed | 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.
Moved: 19 · unchanged at every release: 5
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.