Recordsgolanggithub.com/sirupsen/logrusv1.9.3github.com/sirupsen/logrus.FieldKeyLogrusError
Change the conditions
Current conditions
github.com/sirupsen/logrus.FieldKeyLogrusError @v1.9.3ubuntu glibc · x64 · go 1.26 · go 1
5 of 5 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 5 / 5
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-10
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.7.0 | CHANGED Version changed, no linked failure | contract passed | 27 project-days |
| golang.org/x/sys | v0.0.0-20220715151400-c0bba94af5f8 | CHANGED Version changed, no linked failure | contract passed | 26 project-days |
| golang.org/x/sys | v0.13.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/sys | v0.31.0 | CHANGED Version changed, no linked failure | 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.
| Library | v1.10.2 | v1.9.3 | v1.6.0 | v1.4.2 |
|---|---|---|---|---|
| github.com/konsorten/go-windows-terminal-sequences | — | — | v1.0.3 | v1.0.1 |
| github.com/stretchr/testify | v1.12.1 | v1.7.0 | v1.2.2 | v1.4.0 |
| golang.org/x/sys | v0.13.0 | v0.31.0 | v0.47.0 | v0.18.0 |
Moved: 3 · unchanged at every release: 0
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.