CodeSampleX

Recordsgolanggithub.com/mitchellh/copystructurev1.0.0github.com/mitchellh/copystructure.Copiers

Change the conditions
Fixed
Symbolgithub.com/mitchellh/copystructure.Copiers Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Package versionv1.0.0 Architecturex64 libcglibc Clear filters

Current conditions

github.com/mitchellh/copystructure.Copiers @v1.0.0ubuntu glibc · x64 · go 1.26 · go 1

11 of 11 passed

Observed — real project builds reported from this coordinate.

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

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

v1.0.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:34782db111d49d69d30482bc19c7004b000614af5c8304881c8f167e6380cd85

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/mitchellh/reflectwalk v1.0.0 PASS All observations passed contract passed 9 project-days
github.com/mitchellh/reflectwalk v1.0.2 PASS All observations passed 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.2.0v1.0.0
github.com/mitchellh/reflectwalk v1.0.2 v1.0.2

Moved: 0 · 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