Recordsnpmfind-up-simplefailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
test_contract.go:<n>:<n>: no required module provides package golang.org/x/text/unicode/norm: go.mod file not found in current directory or any parent …
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-05 · Last seen: 2026-09-05
sha256:15e1b71df43a…
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.
- 1.0.1 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-05 → 2026-09-05
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- find-up-simple 1.0.1: findUpSync 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. HOWfindUpSyncnode 22.23.2 MIT-0 · 2026-09-05
- find-up-simple 1.0.1: findUp 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. HOWfindUpnode 22.23.2 MIT-0 · 2026-09-05