CodeSampleX

Sample

Validate map collection size, keys, and values independently in go-playground/validator using dive with keys and endkeys tags

sha256:0c54b02c2dd25ce70f00c1babd01b8a62ad115a471dd335c784e32ac86e55a59

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
Validate map collection size, keys, and values independently in go-playground/validator using dive with keys and endkeys tags HOW
Packages
github.com/go-playground/validator/v10 10.30.3
Environment
go
Created
2026-08-17T18:31:54Z

Commonly assumed

A validation tag placed on a map field or after dive validates both map keys and map values, or applying min on a map validates element length rather than map entry count.

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