Recordsgolanggolang.org/x/netv0.0.0-20200520182314-0ba52f642ac2
Change the conditions
Current conditions
golang.org/x/net @v0.0.0-20200520182314-0ba52f642ac2ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 30 / 32
- Contract verifications
- 0 / 3
- Usage records
- 12
- Independent reporting peers
- 1
- Last recorded
- 2026-10-09
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.0.0-20191011191535-87dc89f01550 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/sys | v0.0.0-20200523222454-059865788121 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/text | v0.3.2 | 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: 4 · unchanged at every release: 0
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.