CodeSampleX

Sample

Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes.

sha256:ddd9c90bd83fb9e4174328cb2f8943e90f9d44f955bffaa56ded31ee00924bf4

PUBLISHED L3_CONTRACT_PASS MIT-0

Execution evidence

Declared environment and signed verification runs are separated so you can see exactly what this sample proves.

Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS

Declared environment

Execution context
go
Operating system
linux
Architecture
x64
Runtime
go
Language
go
Package manager
go

Verification-run environments

Execution context
go 1.26
Operating system
linux alpine · musl
Architecture
x64
Runtime
go 1.26
Language
go
Package manager
go
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17

Case

Goal
Prove Gin 1.12.0 gin.Context.ShouldBindJSON stream consumption behavior, Content-Type independence, empty-body EOF response, and error reporting without automatic response writes. HOW
Packages
github.com/gin-gonic/gin v1.12.0
Environment
go
Created
2026-08-17T22:55:40Z

Commonly assumed

ShouldBindJSON caches the request body to allow multiple binds on the same context, and requires an application/json Content-Type header before parsing.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts