CodeSampleX

Recordsgolanggolang.org/x/modfailure issue

Failure signature

PROJECT_RESOLVE exit 1 ×1

main.go:<n>:<n>: no required module provides package google.golang.org/grpc/cmd/protoc-gen-go-grpc; to add it:

Evidence quality: complete · go/module · resolve-diagnostic · outer go build · First recorded: 2026-08-31 · Last seen: 2026-08-31

sha256:dbc9c0a51e91…

golang.org/x/mod/modfile.Parse

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.

Where it reproduced

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.

Libraryv0.8.0v0.6.0-dev.0.20220419223038-86c51ed26bb4v0.6.0-dev.0.20220106191415-9b9b3d81d5e3v0.4.2v0.3.0
golang.org/x/crypto — v0.3.0 — v0.0.0-20191011191535-87dc89f01550 v0.0.0-20191011191535-87dc89f01550
golang.org/x/tools v0.1.12 v0.1.12 — v0.1.1 v0.0.0-20200825202427-b303f430e36d
golang.org/x/xerrors — — — v0.0.0-20200804184101-5ec99f83aff1 v0.0.0-20200804184101-5ec99f83aff1

Moved: 2 · unchanged at every release: 1

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

Published answers for the affected releases

Back to the package