Recordsgolanggithub.com/mitchellh/copystructure
Change the conditions
Current conditions
github.com/mitchellh/copystructure.Copy @v1.2.0x64 · go 1.26 · go
1 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 came back clean (1)
- Project observations
- 5 / 5
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-21
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
5 of 5 passed
Observed — real project builds reported from this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.2.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/mitchellh/reflectwalk | v1.0.2 | PASS All observations passed | 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.2.0 | v1.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.