Recordsgolanggithub.com/sirupsen/logrusv1.7.0
Change the conditions
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
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.
| Library | v1.10.2 | v1.9.3 | v1.7.0 | v1.6.0 | v1.4.2 | v1.2.0 |
|---|---|---|---|---|---|---|
| github.com/konsorten/go-windows-terminal-sequences | — | — | — | v1.0.3 | v1.0.1 | v1.0.1 |
| github.com/stretchr/testify | v1.12.1 | v1.7.0 | v1.7.0 | v1.2.2 | v1.4.0 | v1.3.0 |
| golang.org/x/sys | v0.13.0 | v0.31.0 | v0.8.0 | v0.47.0 | v0.18.0 | v0.0.0-20190826190057-c7b8b68b1456 |
| golang.org/x/crypto | — | — | — | — | — | v0.0.0-20190308221718-c2843e01d9a2 |
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
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-23 · Last seen: 2026-10-23Diagnostic re-verification candidate