Sample
github.com/spf13/viper v1.21.0: Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default), layer introspection with IsSet and InConfig, and MergeConfig map merging semantics
Verified sample for golang github.com/spf13/viper v1.21.0: Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default)…
sha256:b7af5976c35a3bc3c950214c5b048a213909b113e0078a965324730fe20129e5
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
go linux x64 go go go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-17 |
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
Case
HOW- Goal
- Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default), layer introspection with IsSet and InConfig, and MergeConfig map merging semantics
- Symbols
-
- viper.New
- viper.Set
- viper.BindPFlag
- viper.AutomaticEnv
- viper.ReadConfig
- viper.MergeConfig
- viper.SetDefault
- viper.IsSet
- viper.InConfig
- Environment
- go
- Created
- 2026-08-17T17:43:28Z
Contract
- Viper resolves configuration values following a strict five-tier precedence order where explicit Set overrides bound Flag, Flag overrides AutomaticEnv, Env overrides ReadConfig, and Config overrides SetDefault
- IsSet reports true for keys present in any active source including defaults and environment variables, whereas InConfig only returns true for keys loaded via configuration files
- MergeConfig performs a deep recursive merge on nested map structures while completely replacing slice values with the incoming configuration
Files
- NOTES.md
- csx.json
- go.mod
- go.sum
- precedence_test.go