Recordsgolanggithub.com/go-kit/log
Change the conditions
Current conditions
github.com/go-kit/log.With @v0.2.1x64 · go 1.26 · go · go
1 of 2 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 (2)
- Project observations
- 0 / 1
- Contract verifications
- 1 / 2
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-09-07
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · go 1.26 · go · go
0 of 1 passed
Verified — this network ran a contract at 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
v0.2.1
linux · go@1.26
1 FAIL · stage: PROJECT_PROCESS
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.
| Library | v0.2.1 | v0.2.0 | v0.1.0 |
|---|---|---|---|
| github.com/go-logfmt/logfmt | v0.5.1 | v0.5.1 | v0.5.0 |
| github.com/go-stack/stack | — | — | v1.8.0 |
Moved: 1 · unchanged at every release: 1
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.