Recordsgolanggolang.org/x/cryptov0.57.0golang.org/x/crypto/bcrypt.MaxCost
Change the conditions
Current conditions
golang.org/x/crypto/bcrypt.MaxCost @v0.57.0debian glibc · x64 · go 1.26 · go · go
1 of 1 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 (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-11-08
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/net | v0.58.0 | CHANGED Version changed, no linked failure | 19 project-days | |
| golang.org/x/sys | v0.48.0 | CHANGED Version changed, no linked failure | 19 project-days | |
| golang.org/x/term | v0.46.0 | CHANGED Version changed, no linked failure | 19 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: 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.