Recordsgolanggolang.org/x/cryptov0.0.0-20210711020723-a769d52b0f97golang.org/x/crypto/bcrypt.DefaultCost
Change the conditions
Current conditions
golang.org/x/crypto/bcrypt.DefaultCost @v0.0.0-20210711020723-a769d52b0f97ubuntu glibc · x64 · go 1.26 · go 1
2 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
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.0.0-20210226172049-e18ecbb05110 | CHANGED Version changed, no linked failure | contract passed | 9 project-days |
| golang.org/x/sys | v0.0.0-20210615035016-665e8c7367d1 | CHANGED Version changed, no linked failure | contract passed | 11 project-days |
| golang.org/x/term | v0.0.0-20201126162022-7de9c90e9dd1 | CHANGED Version changed, no linked failure | contract passed | 10 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.