CodeSampleX

Recordsgolanggoogle.golang.org/appenginev1.4.0

Change the conditions
Fixed
Package versionv1.4.0 Package managergo libcglibc
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo Clear filters

Current conditions

google.golang.org/appengine @v1.4.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v1.4.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:0cc5633d6f9aa11fdb97a30243cae2d23c42f9bbcc21f59ae64b43eea06d4a3e

Library Version Health Measured there Projects
github.com/golang/protobuf v1.4.2 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/golang/protobuf v1.4.3 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
golang.org/x/net v0.0.0-20200625001655-4c5254603344 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
golang.org/x/text v0.3.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
golang.org/x/text v0.3.2 CANDIDATE Correlated change; unproven combination contract passed 11 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.

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