Recordsgolanggolang.org/x/modfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package github.com/pkg/errors (imported by go.step.sm/crypto/randutil); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:2ffeca86330b…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.40.0 not measured
- v0.39.0 not measured
- v0.38.0 not measured
- v0.37.0 FAIL
- v0.35.0 not measured
- v0.34.0 not measured
- v0.31.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.40.0 | v0.39.0 | v0.38.0 | v0.37.0 | v0.35.0 |
|---|---|---|---|---|---|
| golang.org/x/tools | — | v0.49.0 | v0.48.0 | v0.47.0 | v0.44.0 |
Moved: 1 · 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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.