CodeSampleX

Recordsgolanggithub.com/sirupsen/logrusv1.4.2github.com/sirupsen/logrus.FieldKeyMsg

Change the conditions
Fixed
Package versionv1.4.2 Symbolgithub.com/sirupsen/logrus.FieldKeyMsg Architecturex64
Filter OSubuntu glibc Runtimego 1.26 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/sirupsen/logrus.FieldKeyMsg @v1.4.2ubuntu glibc · x64 · go 1.26 · go 1

1 of 1 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
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Changed 9 · Steady 0

Dependency changes observed: 9. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/konsorten/go-windows-terminal-sequences v1.0.1 CHANGED Version changed, no linked failure builds observed 13 project-days
github.com/konsorten/go-windows-terminal-sequences v1.0.2 CHANGED Version changed, no linked failure nothing measured 19 project-days
github.com/stretchr/testify v1.2.2 CHANGED Version changed, no linked failure nothing measured 13 project-days
github.com/stretchr/testify v1.7.0 CHANGED Version changed, no linked failure contract passed 11 project-days
github.com/stretchr/testify v1.8.1 CHANGED Version changed, no linked failure contract passed 11 project-days
golang.org/x/sys v0.0.0-20190422165155-953cdadca894 CHANGED Version changed, no linked failure builds observed 13 project-days
golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1 CHANGED Version changed, no linked failure contract passed 10 project-days
golang.org/x/sys v0.17.0 CHANGED Version changed, no linked failure contract passed 9 project-days
golang.org/x/sys v0.18.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.

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.