CodeSampleX

Recordscargoclap4.6.6ArgAction::Set

Change the conditions
Fixed
Package version4.6.6 SymbolArgAction::Set
Filter OSalpine musl Runtimerust 1 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

ArgAction::Set @4.6.6alpine musl · x64 · rust 1 · cargo · rust

2 of 4 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (2)

Project observations
0 / 1
Contract verifications
2 / 4
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

4.6.6

linux · rust@1 · executionContext=rust

1 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
clap_builder 4.6.6 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
clap_derive 4.6.4 CANDIDATE Correlated change; unproven combination contract passed 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.

Library4.6.74.6.64.6.44.6.0
clap_builder 4.6.7 4.6.6 4.6.2 4.6.0
clap_derive 4.6.7 4.6.4 — —

Moved: 2 · unchanged at every release: 0

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