CodeSampleX

Recordsgolanggithub.com/sirupsen/logrusv1.9.3

Change the conditions
Fixed
Package versionv1.9.3 Symbolwhole package
Filter OSalpine musl Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

github.com/sirupsen/logrus @v1.9.3alpine musl · 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (6)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 0

Dependency changes observed: 3. 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 6 project-days
golang.org/x/sys v0.0.0-20220715151400-c0bba94af5f8 CHANGED Version changed, no linked failure nothing measured 6 project-days
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.

Libraryv1.9.3v1.6.0v1.4.2
github.com/konsorten/go-windows-terminal-sequences — v1.0.3 v1.0.1
github.com/stretchr/testify v1.7.0 v1.2.2 v1.8.1
golang.org/x/sys 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.