Recordsgolanggolang.org/x/termfailure issue
Failure signature
PROJECT_PROCESS exit 1 ERR_MODULE_NOT_FOUND ×1
node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …
Evidence quality: complete · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:c33691aec18d…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.22.0 not measured
- v0.17.0 not measured
- v0.2.0 PASS 3 passing observations
- v0.0.0-20210927222741-03fcf44c2211 FAIL
- v0.0.0-20201126162022-7de9c90e9dd1 PASS 4 passing observations
- v0.0.0-20201117132131-f5c789dd3221 PASS 3 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-29 → 2026-08-29
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.0.0-20201126162022-7de9c90e9dd1 → first failing release v0.0.0-20210927222741-03fcf44c2211
What differs across the boundary
- golang.org/x/sys v0.0.0-20201119102817-f84b799fce68, v0.0.0-20210330210617-4fbd30eecc44, v0.0.0-20210510120138-977fb7262007, v0.0.0-20210615035016-665e8c7367d1, v0.0.0-20210806184541-e5e7981a1069, v0.47.0, v0.48.0, v0.8.0, v0.9.0 → v0.0.0-20210615035016-665e8c7367d1 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.0.0-20210927222741-03fcf44c2211 → first passing release v0.2.0
What differs across the boundary
- golang.org/x/sys v0.2.0 → v0.0.0-20210615035016-665e8c7367d1 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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.22.0 | v0.17.0 | v0.2.0 | v0.0.0-20210927222741-03fcf44c2211 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201117132131-f5c789dd3221 |
|---|---|---|---|---|---|---|
| golang.org/x/sys | v0.22.0 | v0.17.0 | v0.2.0 | v0.0.0-20210615035016-665e8c7367d1 | v0.8.0 | v0.0.0-20191026070338-33540a1f6037 |
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
- Releases in this window never measured at PROJECT_PROCESS: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/term v0.0.0-20210927222741-03fcf44c2211: Restore This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/term.Restorego 1.26.6 MIT-0 · 2026-09-04
- golang.org/x/term v0.0.0-20210927222741-03fcf44c2211: ReadPassword This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/term.ReadPasswordgo 1.26.6 MIT-0 · 2026-09-04
- golang.org/x/term v0.0.0-20210927222741-03fcf44c2211: MakeRaw This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/term.MakeRawgo 1.26.6 MIT-0 · 2026-09-04