Recordsgolanggoogle.golang.org/appenginev1.4.0
Change the conditions
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
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.
| Library | v1.6.6 | v1.4.0 |
|---|---|---|
| github.com/golang/protobuf | v1.5.0 | v1.4.2 |
| golang.org/x/net | v0.0.0-20210525063256-abc453219eb5 | v0.0.0-20200625001655-4c5254603344 |
| golang.org/x/text | v0.3.6 | v0.3.0 |
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 UNKNOWN exit 1 Evidence gap ×1 v1.4.0 os=linux · runtime=go@1.26 sha256:0cc5633d6f9a…Contract test failed: expected JSON output to mask secret with <str>, got <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v1.4.0 os=linux · runtime=go@1.26 sha256:57f8400667e3…<path> declared and not used: gotAuthgo/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05