Records/golang/github.com/spf13/viper/v1.21.0/github.com/spf13/viper.NewWithOptions

Published samples

• github.com/spf13/viper v1.21.0: Show that delimiter-aware key lookup state is preserved when taking a Viper sub-tree. Built ? 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. HOWgithub.com/spf13/viper.Newgithub.com/spf13/viper.NewWithOptionsgithub.com/spf13/viper.KeyDelimitergithub.com/spf13/viper.Viper.Subgithub.com/spf13/viper.Viper.GetStringgo MIT-0 · 2026-08-16

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-15

Failure clusters

• observed PROJECT_TEST Evidence gap ×1 v1.21.0 executionContext=go · os=linux · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-08 · Last seen: 2026-09-08
  Where does this failure start and stop?