CodeSampleX

Sample

Prove that Caddy's filter log encoder wraps underlying encoders to filter, delete, replace, mask, and rename structured log fields using '>' nested path syntax.

sha256:43564a14d06c65a07493b28abf1011627599d52615a92d681137959fab6ef337

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 that Caddy's filter log encoder wraps underlying encoders to filter, delete, replace, mask, and rename structured log fields using '>' nested path syntax. HOW
Packages
github.com/caddyserver/caddy/v2 2.11.4
Environment
go
Created
2026-08-17T22:41:53Z

Commonly assumed

The filter log encoder requires an explicit wrapped encoder format and uses dot notation for nested log field paths.

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