Recordsgolanggithub.com/spf13/viperv1.21.0github.com/spf13/viper.RemoteProvider
Change the conditions
Current conditions
github.com/spf13/viper.RemoteProvider @v1.21.0windows 11 · x64 · go 1.26 · go 1
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.21.0
linux · go@1.26 · executionContext=go
1 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/fsnotify/fsnotify | v1.9.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/spf13/afero | v1.15.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/spf13/cast | v1.10.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/spf13/pflag | v1.0.10 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/subosito/gotenv | v1.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/go-viper/mapstructure/v2 | v2.4.0 | PASS All observations passed | contract passed | 4 project-days |
| github.com/pelletier/go-toml/v2 | v2.2.4 | PASS All observations passed | builds observed | 4 project-days |
| github.com/sagikazarmark/locafero | v0.11.0 | PASS All observations passed | contract passed | 4 project-days |
| go.yaml.in/yaml/v3 | v3.0.4 | PASS All observations passed | contract passed | 4 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.