Recordsgolanggolang.org/x/expv0.0.0-20260824195058-e88cd73687aagolang.org/x/exp/ebnf.Parse
Change the conditions
Current conditions
golang.org/x/exp/ebnf.Parse @v0.0.0-20260824195058-e88cd73687aadebian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.0-20260824195058-e88cd73687aa
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| golang.org/x/mod | v0.39.0 | CANDIDATE Correlated change; unproven combination | builds observed | 4 project-days |
| golang.org/x/tools | v0.49.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| golang.org/x/tools/go/packages/packagestest | v0.1.1-deprecated | UNKNOWN No linked outcome measured | nothing measured | 4 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.0.0-20260824195058-e88cd73687aa | v0.0.0-20251023183803-a4bb9ffd2546 | v0.0.0-20240506185415-9bf2ced13842 | v0.0.0-20230515195305-f3d0a9c9a5cc | v0.0.0-20200224162631-6cc2880d07d6 |
|---|---|---|---|---|---|
| github.com/google/go-cmp | v0.6.0 | v0.7.0 | v0.6.0 | v0.6.0 | — |
| golang.org/x/mod | v0.39.0 | v0.37.0 | v0.17.0 | v0.6.0 | v0.2.0 |
| golang.org/x/tools | v0.49.0 | v0.46.0 | v0.21.0 | v0.2.0 | v0.0.0-20200825202427-b303f430e36d |
| dmitri.shuralyov.com/gpu/mtl | — | — | — | — | v0.0.0-20190408044501-666a987793e9 |
| github.com/BurntSushi/xgb | — | — | — | — | v0.0.0-20160522181843-27f122750802 |
| github.com/go-gl/glfw/v3.3/glfw | — | — | — | — | v0.0.0-20200222043503-6f7a984d4dc4 |
| golang.org/x/image | — | — | — | — | v0.0.0-20190802002840-cff245a6509b |
| golang.org/x/mobile | — | — | — | — | v0.0.0-20190719004257-d2bd2a29d028 |
| golang.org/x/sys | — | — | — | — | v0.47.0 |
| golang.org/x/tools/go/packages/packagestest | v0.1.1-deprecated | v0.1.1-deprecated | — | — | — |
| golang.org/x/xerrors | — | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 |
Moved: 3 · unchanged at every release: 8
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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v0.0.0-20260824195058-e88cd73687aa os=linux · runtime=go@1.26 sha256:d5fae02e8604…test/contract.go:<n>:<n>: <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.0.0-20260824195058-e88cd73687aa os=linux · runtime=go@1.26 sha256:042f6e977a16…go: updates to go.mod needed; to update it: · go mod tidygo · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate