CodeSampleX

Recordsgolanggolang.org/x/netv0.52.0golang.org/x/net/publicsuffix.List

Change the conditions
Fixed
Symbolgolang.org/x/net/publicsuffix.List Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package versionv0.52.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

golang.org/x/net/publicsuffix.List @v0.52.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 40 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
38 / 39
Contract verifications
0 / 40
Independent reporting peers
3
Last recorded
2026-09-02

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 4 · Steady 0

First observed break

v0.52.0 golang.org/x/crypto@v0.49.0

linux

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

Library Version Health Measured there Projects
golang.org/x/crypto v0.49.0 FAIL Linked failure observed; version changed across releases nothing measured 17 project-days
golang.org/x/sys v0.42.0 FAIL Linked failure observed; version changed across releases contract passed 17 project-days
golang.org/x/term v0.41.0 FAIL Linked failure observed; version changed across releases nothing measured 17 project-days
golang.org/x/text v0.35.0 FAIL Linked failure observed; version changed across releases contract passed 17 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.

Recent failure clusters