CodeSampleX

Recordsgolanggithub.com/spf13/aferov1.15.0github.com/spf13/afero.Fs

Change the conditions
Fixed
Package versionv1.15.0 Symbolgithub.com/spf13/afero.Fs
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

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

22 of 22 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
22 / 22
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-09
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v1.15.0

linux · go@1.26

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/text v0.28.0 CANDIDATE Correlated change; unproven combination contract passed 6 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.

Libraryv1.15.0v1.3.3
golang.org/x/text v0.28.0 v0.3.7
github.com/pkg/sftp — v1.10.1
golang.org/x/crypto — v0.0.0-20190820162420-60c769a6c586

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