CodeSampleX

Recordsgolanggithub.com/spf13/viper

Change the conditions
Fixed
Package versionv1.7.0 Package managergo
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/spf13/viper @v1.7.0debian glibc · x64 · go 1.26 · go · go

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
2 / 2
Contract verifications
2 / 2
Usage records
3
Independent reporting peers
1
Last recorded
2026-10-28

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 10 · Steady 6

Dependency changes observed: 10. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/fsnotify/fsnotify v1.4.7 CHANGED Version changed, no linked failure contract passed 6 project-days
github.com/magiconair/properties v1.8.1 CHANGED Version changed, no linked failure contract passed 7 project-days
github.com/spf13/afero v1.1.2 CHANGED Version changed, no linked failure contract passed 5 project-days
github.com/spf13/cast v1.3.0 CHANGED Version changed, no linked failure contract passed 7 project-days
github.com/spf13/pflag v1.0.3 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/spf13/pflag v1.0.5 CHANGED Version changed, no linked failure contract passed 6 project-days
github.com/stretchr/testify v1.3.0 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/stretchr/testify v1.7.0 CHANGED Version changed, no linked failure contract passed 6 project-days
github.com/subosito/gotenv v1.2.0 CHANGED Version changed, no linked failure contract passed 6 project-days
gopkg.in/yaml.v2 v2.4.0 CHANGED Version changed, no linked failure contract passed 6 project-days
github.com/bketelsen/crypt v0.0.3-0.20200106085610-5cbc8cc4026c PASS All observations passed contract passed 7 project-days
github.com/hashicorp/hcl v1.0.0 PASS All observations passed contract passed 7 project-days
github.com/mitchellh/mapstructure v1.1.2 PASS All observations passed contract passed 7 project-days
github.com/pelletier/go-toml v1.2.0 PASS All observations passed contract passed 6 project-days
github.com/spf13/jwalterweatherman v1.0.0 PASS All observations passed contract passed 5 project-days
gopkg.in/ini.v1 v1.51.0 PASS All observations passed contract passed 6 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 8 · unchanged at every release: 11

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.