Recordsgolanggolang.org/x/crypto/x509roots/fallbackfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
roots.go:<n>:<n>: missing go.sum entry for module providing package golang.<token> (imported by example.com/roots); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:9e4a7bc5728d…
golang.org/x/crypto/x509roots/fallback/bundle.Roots
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.
- v0.0.0-20260213171211-a408498e5541 FAIL
- v0.0.0-20250305170421-49bf5b80c810 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
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.
- Releases in this window never measured at PROJECT_RESOLVE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto/x509roots/fallback v0.0.0-20260213171211-a408498e5541: iterate NSS root certificates and construct x509 cert pool with constraints using bundle.Roots 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/crypto/x509roots/fallback/bundle.Roots MIT-0 · 2026-08-28