CodeSampleX

Recordsgolanggolang.org/x/cryptofailure 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-08-31

sha256:88af852f99a8…

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.

Libraryv0.33.0v0.31.0v0.27.0v0.26.0v0.25.0v0.3.0v0.0.0-20220525230936-793ad666bf5ev0.0.0-20220331220935-ae2d96664a29v0.0.0-20210921155107-089bfa567519
golang.org/x/net v0.21.0 v0.21.0 v0.21.0 — v0.21.0 v0.2.0 v0.0.0-20211112202133-69e39bad7dc2 — v0.4.0
golang.org/x/sys v0.30.0 v0.28.0 v0.25.0 — v0.22.0 v0.2.0 v0.0.0-20220608164250-635b8c9b7f68 — v0.47.0
golang.org/x/term v0.29.0 v0.27.0 v0.24.0 — v0.22.0 v0.2.0 v0.0.0-20201126162022-7de9c90e9dd1 — v0.0.0-20210927222741-03fcf44c2211

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.

Evidence gaps

Published answers for the affected releases

Back to the package