CodeSampleX

Recordsgolanggithub.com/spf13/aferov1.3.3

Change the conditions
Fixed
OSubuntu glibc Package versionv1.3.3 Package managergo 1
Filter Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

github.com/spf13/afero @v1.3.3ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
7 / 7
Contract verifications
0 / 1
Usage records
2
Independent reporting peers
1
Last recorded
2026-10-11

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

v1.3.3

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:bea3da8064e5346f265e3a89c056b6b7d5f1267fc192d3ef6a85b2dd403e4716

Library Version Health Measured there Projects
golang.org/x/text v0.3.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/pkg/sftp v1.10.1 PASS All observations passed builds observed 3 project-days
golang.org/x/crypto v0.0.0-20190820162420-60c769a6c586 PASS All observations passed builds observed 3 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: 1 · unchanged at every release: 2

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