Recordsgolanggithub.com/spf13/afero
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
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 | 3 project-days | |
| github.com/pkg/sftp | v1.10.1 | UNKNOWN No linked outcome measured | 3 project-days | |
| golang.org/x/crypto | v0.0.0-20190820162420-60c769a6c586 | UNKNOWN No linked outcome measured | 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.
| Library | v1.15.0 | v1.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.