Recordscargoclap_builder
Change the conditions
Current conditions
clap_builder @4.6.6ubuntu glibc · x64 · cargo 1
0 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 4 / 6
- Contract verifications
- 0 / 3
- Independent reporting peers
- 1
- Last recorded
- 2026-10-11
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 3 passed
Verified — this network ran a contract at this coordinate.
-
0 of 3 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.6.6
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:a6f8d9fae67c4917010b43e8429074116ec3c9b7ea6d43b8294dd4e20f837ce8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| clap_lex | 1.1.0 | UNKNOWN No linked outcome measured | nothing measured | 4 project-days |
| anstream | 1.0.0 | PASS All observations passed | contract passed | 8 project-days |
| anstyle | 1.0.14 | PASS All observations passed | contract passed | 8 project-days |
| clap_lex | 1.1.1 | PASS All observations passed | contract passed | 3 project-days |
| strsim | 0.11.1 | PASS All observations passed | contract passed | 7 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 | 4.6.7 | 4.6.6 | 4.6.2 | 4.6.0 |
|---|---|---|---|---|
| anstream | 1.0.0 | 1.0.0 | 1.0.0 | — |
| anstyle | 1.0.14 | 1.0.14 | 1.0.14 | 1.0.14 |
| clap_lex | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 |
| strsim | 0.11.1 | 0.11.1 | 0.11.1 | — |
Moved: 0 · unchanged at every release: 4
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.