CodeSampleX

Recordsgolanggoogle.golang.org/protobuffailure issue

Failure signature

UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×5

node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …

Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-29 · Last seen: 2026-09-05

sha256:88af852f99a8…

google.golang.org/protobuf/encoding/protojson.Marshal google.golang.org/protobuf/encoding/protojson.Unmarshal google.golang.org/protobuf/proto.Clone google.golang.org/protobuf/proto.Equal google.golang.org/protobuf/proto.Float64 google.golang.org/protobuf/proto.Marshal google.golang.org/protobuf/proto.Unmarshal

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN 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.

Libraryv1.36.12v1.36.11v1.36.10v1.32.0v1.31.0v1.28.0v1.26.0v1.26.0-rc.1
github.com/golang/protobuf v1.5.2 v1.5.3 v1.5.4 v1.5.0 v1.5.3 v1.5.3 v1.5.3 —
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.5.5 v0.5.9 v0.6.0 v0.5.5 v0.5.5

Moved: 2 · 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

Published answers for the affected releases

Back to the package