Recordsgolanggoogle.golang.org/protobufv1.36.11
Change the conditions
Current conditions
google.golang.org/protobuf @v1.36.11ubuntu glibc · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (11)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.36.11
linux
17 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 112 project-days |
| github.com/golang/protobuf | v1.5.3 | CANDIDATE Correlated change; unproven combination | builds observed | 38 project-days |
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 115 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 305 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 | v1.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 | v1.35.2 | v1.35.1 | v1.34.2 | v1.33.0 | v1.32.0 | v1.31.0 | v1.28.0 | v1.26.0 | v1.26.0-rc.1 | v1.25.0 | v1.24.0 | v1.23.0 | v1.22.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.3 | v1.5.4 | v1.5.4 | v1.5.4 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.2 | v1.5.0 | v1.5.3 | v1.5.3 | v1.5.3 | — | v1.4.2 | v1.4.2 | v1.4.0 | v1.4.1 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 | v0.6.0 | v0.6.0 | v0.5.5 | v0.6.0 | v0.5.5 | v0.5.9 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.1 | v0.4.1 | v0.4.0 | v0.4.0 |
| google.golang.org/genproto | — | — | — | — | — | — | — | — | — | — | — | — | — | — | v0.0.0-20200804131852-c06518451d9c | v0.0.0-20200618031413-b414f8b61790 | — | — |
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.
Recent failure clusters
-
observed PROCESS_START process start failed Evidence gap ×17 v1.28.0 → v1.36.11 os=linux sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-30 · Last seen: 2026-09-08Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×15 v1.28.0 → v1.36.11 executionContext=node · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7 v1.28.0 → v1.36.11 os=linuxEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-26 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 v1.28.0 → v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 2 EVERYTHING Evidence gap ×3 v1.28.0 → v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:d29a2deca319…csx sample: unknown subcommand <str> · usage: csx sample <subcommand> · propose --goal G [--package purl]... [--symbol s]... …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×3 v1.36.11 → v1.36.12 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 v1.36.11 → v1.36.12 os=linux sha256:3b3190f2cd44…doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)go · unclassified-diagnostic · outer go · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-05 · Last seen: 2026-10-14Diagnostic re-verification candidate
-
observed UNKNOWN exit 2 Evidence gap ×2 v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:5bb159dc4015…usage: -c [-h] [--port int] · -c: error: unrecognized arguments: -p 4000· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:7789edf7d3db…<path> · <path> · <path>· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:814955cf0a3e…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:098fc7e854ba…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: style backgroundColor must matchnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ERESOLVE ×1 v1.36.11 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:3c31643e02d8…npm error code ERESOLVEnode/npm · resolve-diagnostic · outer npm installEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
Showing the 12 most-reported of 28 recorded failure clusters. The rest are single reports.