Recordsgolanggo.uber.org/mockv0.6.0
Change the conditions
Current conditions
go.uber.org/mock @v0.6.0linux · glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 10 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 0 / 10
- Contract verifications
- nothing at this coordinate
- Usage records
- 17
- Independent reporting peers
- 1
- Last recorded
- 2026-09-02
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.6.0
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:ef468617c7e63453868e004f3489e109835732c4441883f0f9116d85a130eba7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| golang.org/x/mod | v0.32.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 5 project-days |
| golang.org/x/mod | v0.35.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/tools | v0.41.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 5 project-days |
| golang.org/x/tools | v0.44.0 | CANDIDATE Correlated change; unproven combination | contract passed | 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.
| Library | v0.6.0 | v0.5.2 | v0.5.0 |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.12.1 | v1.9.0 |
| golang.org/x/mod | v0.35.0 | v0.18.0 | v0.18.0 |
| golang.org/x/tools | v0.44.0 | v0.22.0 | v0.31.0 |
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
-
observed PROJECT_RESOLVE exit 1 ×2 v0.6.0 os=linux · runtime=go@1.26 sha256:ef468617c7e6…<path> missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/randutil); to add:go/module · resolve-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_RESOLVE exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:c7d4da684991…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/pemutil); to add: …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed PROJECT_RESOLVE exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:de2bcfa430eb…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/pemutil); to add:go/module · resolve-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:defe7abc6f40…FAIL example.com/pemutil_contract [setup failed]go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_RESOLVE exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:6273c77e0993…<path> missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/keyutil); to add:go/module · resolve-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:65e540a1f555…FAIL explore [setup failed]go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:2a465d4e02b1…FAIL test_randutil [setup failed]go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:924d57406bad…FAIL test-randutil [setup failed]go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_RESOLVE exit 1 ×1 v0.6.0 os=linux · runtime=go@1.26 sha256:2ffeca86330b…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/randutil); to add:go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02