CodeSampleX

Sample

Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing

sha256:46df4736d445e122bed613d66d9074610072b234cffa56ec4013cd41d2affee5

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
Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing HOW
Packages
go.uber.org/zap 1.27.0
Environment
go
Created
2026-08-17T11:48:38Z

Commonly assumed

zap.Config.Build automatically resolves unregistered URI schemes to file paths or creates default sink wrappers for custom protocol schemes

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