Recordsgolanggithub.com/Masterminds/sprig/v3v3.2.3github.com/Masterminds/sprig/v3.GenericFuncMap
Change the conditions
Current conditions
github.com/Masterminds/sprig/v3.GenericFuncMap @v3.2.3debian glibc · x64 · go 1.26 · go · go
1 of 1 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 (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 9. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/Masterminds/semver/v3 | v3.2.0 | CHANGED Version changed, no linked failure | contract passed | 4 project-days |
| github.com/huandu/xstrings | v1.3.3 | CHANGED Version changed, no linked failure | contract passed | 4 project-days |
| github.com/shopspring/decimal | v1.2.0 | CHANGED Version changed, no linked failure | contract passed | 4 project-days |
| github.com/spf13/cast | v1.3.1 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/spf13/cast | v1.4.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/stretchr/testify | v1.5.1 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.9.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/crypto | v0.22.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/crypto | v0.3.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/Masterminds/goutils | v1.1.1 | PASS All observations passed | contract passed | 4 project-days |
| github.com/google/uuid | v1.1.1 | PASS All observations passed | contract passed | 3 project-days |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 1 project-day |
| github.com/imdario/mergo | v0.3.11 | PASS All observations passed | contract passed | 3 project-days |
| github.com/imdario/mergo | v0.3.12 | PASS All observations passed | contract passed | 1 project-day |
| github.com/mitchellh/copystructure | v1.0.0 | PASS All observations passed | contract passed | 3 project-days |
| github.com/mitchellh/copystructure | v1.2.0 | PASS All observations passed | contract passed | 1 project-day |
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: 6 · unchanged at every release: 5
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.