Recordsgolanggithub.com/Masterminds/sprig/v3v3.3.0
Change the conditions
Current conditions
github.com/Masterminds/sprig/v3 @v3.3.0alpine musl · x64 · go 1.26 · go · go
package-level total, not an API
3 of 3 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 (3)
- Project observations
- 2 / 2
- Contract verifications
- 3 / 3
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| dario.cat/mergo | v1.0.2 | contract passed | 2 project-days |
| github.com/Masterminds/goutils | v1.1.1 | contract passed | 2 project-days |
| github.com/Masterminds/semver/v3 | v3.4.0 | builds observed | 2 project-days |
| github.com/google/uuid | v1.6.0 | contract passed | 2 project-days |
| github.com/huandu/xstrings | v1.5.0 | contract passed | 2 project-days |
| github.com/mitchellh/copystructure | v1.2.0 | contract passed | 2 project-days |
| github.com/shopspring/decimal | v1.4.0 | contract passed | 2 project-days |
| github.com/spf13/cast | v1.7.0 | contract passed | 2 project-days |
| github.com/stretchr/testify | v1.11.1 | contract passed | 2 project-days |
| golang.org/x/crypto | v0.52.0 | contract passed | 2 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.