Recordsgolanggithub.com/spf13/viperv1.21.0
Change the conditions
Current conditions
github.com/spf13/viper @v1.21.0alpine musl · x64 · go 1.26 · go · go
package-level total, not an API
8 of 11 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (5)
- Project observations
- 9 / 10
- Contract verifications
- 8 / 11
- Usage records
- 4
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 10
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 | PASS All observations passed | 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 | builds observed | 4 project-days |
| github.com/spf13/afero | v1.15.0 | PASS All observations passed | builds observed | 4 project-days |
| github.com/spf13/cast | v1.10.0 | PASS All observations passed | contract passed | 4 project-days |
| github.com/spf13/pflag | v1.0.10 | PASS All observations passed | contract passed | 4 project-days |
| github.com/stretchr/testify | v1.11.1 | PASS All observations passed | contract passed | 4 project-days |
| github.com/subosito/gotenv | v1.6.0 | PASS All observations passed | builds observed | 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.
Recent failure clusters
-
observed PROJECT_TEST Evidence gap ×1 v1.21.0 executionContext=go · os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-08 · Last seen: 2026-09-08