Recordsgolanggoogle.golang.org/genprotov0.0.0-20190306203927-b5d61aea6440
Change the conditions
Current conditions
google.golang.org/genproto @v0.0.0-20190306203927-b5d61aea6440debian 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: 13. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.2.0 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| github.com/golang/protobuf | v1.3.1 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/golang/protobuf | v1.5.4 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/lint | v0.0.0-20190227174305-5b3e6a55c961 | CHANGED Version changed, no linked failure | builds observed | 8 project-days |
| golang.org/x/net | v0.0.0-20190213061140-3a22650c66bd | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/net | v0.0.0-20190313220215-9f648a60d977 | CHANGED Version changed, no linked failure | builds observed | 4 project-days |
| golang.org/x/net | v0.38.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/tools | v0.0.0-20190226205152-f727befe758c | CHANGED Version changed, no linked failure | builds observed | 7 project-days |
| golang.org/x/tools | v0.31.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/grpc | v1.19.0 | CHANGED Version changed, no linked failure | builds observed | 7 project-days |
| google.golang.org/grpc | v1.67.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| honnef.co/go/tools | v0.0.0-20190102054323-c2f93a96b099 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| honnef.co/go/tools | v0.0.0-20190106161140-3f1c8253044a | CHANGED Version changed, no linked failure | nothing measured | 6 project-days |
| golang.org/x/exp | v0.0.0-20190121172915-509febef88a4 | UNKNOWN No linked outcome measured | nothing measured | 4 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.
Moved: 12 · 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.