Recordsgolanggolang.org/x/net
Change the conditions
Current conditions
golang.org/x/net/html.NewTokenizer @v0.17.0ubuntu glibc · x64 · node
0 of 25 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
- 2 / 2
- Contract verifications
- 0 / 25
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
0 of 14 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 11 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.17.0
linux
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.14.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| golang.org/x/sys | v0.13.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 4 project-days |
| golang.org/x/sys | v0.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/term | v0.13.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| golang.org/x/text | v0.13.0 | CANDIDATE Correlated change; unproven combination | builds observed | 6 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: 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.