CodeSampleX

Recordsgolanggolang.org/x/netv0.0.0-20220403103023-749bd193bc2bgolang.org/x/net/idna.ToUnicode

Change the conditions
Fixed
Runtimenode 22 Package versionv0.0.0-20220403103023-749bd193bc2b Symbolgolang.org/x/net/idna.ToUnicode
Filter OSubuntu glibc Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

golang.org/x/net/idna.ToUnicode @v0.0.0-20220403103023-749bd193bc2bubuntu glibc · x64 · node 22 · npm 10 · node

0 of 35 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
25 / 25
Contract verifications
0 / 35
Independent reporting peers
3
Last recorded
2026-08-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

v0.0.0-20220403103023-749bd193bc2b

linux

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

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.

Libraryv0.58.0v0.57.0v0.55.0v0.53.0v0.52.0v0.51.0v0.50.0v0.37.0v0.35.0v0.34.0v0.29.0v0.21.0v0.17.0v0.12.0v0.4.0v0.0.0-20210525063256-abc453219eb5v0.0.0-20200625001655-4c5254603344
golang.org/x/crypto v0.55.0 v0.54.0 v0.52.0 v0.50.0 v0.49.0 v0.48.0 v0.48.0 v0.36.0 v0.33.0 v0.32.0 v0.27.0 v0.20.0 v0.14.0 v0.11.0 v0.0.0-20200622213623-75b288015ac9
golang.org/x/sys v0.47.0 v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 v0.41.0 v0.31.0 v0.30.0 v0.29.0 v0.25.0 v0.17.0 v0.13.0 v0.10.0 v0.47.0 v0.47.0 v0.0.0-20210603081109-ebe580a85c40
golang.org/x/term v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.41.0 v0.40.0 v0.40.0 v0.30.0 v0.29.0 v0.28.0 v0.24.0 v0.17.0 v0.13.0 v0.10.0 v0.0.0-20201126162022-7de9c90e9dd1
golang.org/x/text v0.41.0 v0.40.0 v0.37.0 v0.36.0 v0.35.0 v0.34.0 v0.34.0 v0.23.0 v0.22.0 v0.21.0 v0.18.0 v0.14.0 v0.13.0 v0.11.0 v0.5.0 v0.3.6 v0.3.2

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