CodeSampleX

Recordsgolanggithub.com/sirupsen/logrusv1.7.0

Change the conditions
Fixed
Package versionv1.7.0 Package managergo
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/sirupsen/logrus @v1.7.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-10-23

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

v1.7.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:0882784d80c20e919569b4a9a1a5ff54eb0aa7665750aedc7afd0bce723472f8

Library Version Health Measured there Projects
github.com/stretchr/testify v1.7.0 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
golang.org/x/sys v0.0.0-20210806184541-e5e7981a1069 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
golang.org/x/sys v0.8.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/sys v0.9.0 CANDIDATE Correlated change; unproven combination contract passed 5 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: 3 · 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.

Recent failure clusters