Recordsgolanggithub.com/Masterminds/sprig/v3
Change the conditions
Current conditions
github.com/Masterminds/sprig/v3.TxtFuncMap @v3.3.0x64 · go 1.26 · 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
- 4 / 4
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-21
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
4 of 4 passed
Observed — real project builds reported from this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v3.3.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:44a92da7386c2265264a1013c792989fdd20ea40dc02db1c242837483e5662e4
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/Masterminds/semver/v3 | v3.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/Masterminds/semver/v3 | v3.4.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/huandu/xstrings | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/shopspring/decimal | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/spf13/cast | v1.7.0 | 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 |
| golang.org/x/crypto | v0.50.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/crypto | v0.52.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/crypto | v0.54.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| dario.cat/mergo | v1.0.1 | PASS All observations passed | contract passed | 2 project-days |
| dario.cat/mergo | v1.0.2 | PASS All observations passed | contract passed | 2 project-days |
| github.com/Masterminds/goutils | v1.1.1 | PASS All observations passed | contract passed | 4 project-days |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 4 project-days |
| github.com/mitchellh/copystructure | v1.2.0 | 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: 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.