CodeSampleX

Recordsgolanggolang.org/x/cryptov0.27.0

Change the conditions
Fixed
OSalpine musl Package versionv0.27.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

golang.org/x/crypto @v0.27.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

7 of 7 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (9)

Project observations
6 / 6
Contract verifications
7 / 7
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-04
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 3 · Steady 0

First observed break

v0.27.0 golang.org/x/net@v0.21.0

linux

13 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/net v0.21.0 FAIL Linked failure observed; version changed across releases contract passed 2 project-days
golang.org/x/sys v0.25.0 FAIL Linked failure observed; version changed across releases nothing measured 2 project-days
golang.org/x/term v0.24.0 FAIL Linked failure observed; version changed across releases nothing measured 2 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.

Libraryv0.55.0v0.54.0v0.52.0v0.50.0v0.48.0v0.36.0v0.27.0v0.20.0v0.19.0v0.0.0-20210921155107-089bfa567519v0.0.0-20210322153248-0c34fe9e7dc2v0.0.0-20200622213623-75b288015ac9v0.0.0-20191011191535-87dc89f01550
golang.org/x/net v0.57.0 v0.57.0 v0.55.0 v0.53.0 v0.50.0 v0.21.0 v0.21.0 v0.21.0 v0.21.0 v0.4.0 v0.0.0-20210226172049-e18ecbb05110 v0.0.0-20210525063256-abc453219eb5 v0.0.0-20190620200207-3b0461eec859
golang.org/x/sys v0.47.0 v0.47.0 v0.45.0 v0.43.0 v0.41.0 v0.31.0 v0.25.0 v0.17.0 v0.17.0 v0.47.0 v0.0.0-20201119102817-f84b799fce68 v0.47.0 v0.0.0-20190412213103-97732733099d
golang.org/x/term v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.40.0 v0.30.0 v0.24.0 v0.17.0 v0.17.0 — v0.0.0-20201126162022-7de9c90e9dd1 — —

Moved: 3 · 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