Recordscargoclap4.6.4
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | |
|---|---|---|
| clap::Arg | 100%1 | 83%6 |
| clap::ArgAction | 83%6 | |
| clap::Args | 100%2 | |
| clap::Command | 100%1 | 88%8 |
| clap::CommandFactory | 100%1 | |
| clap::FromArgMatches | 100%3 |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_PROCESS 5✓ · PROJECT_TEST 4✓ 1✕
|
LOW | 10 | 0 | 90% | 1 | 2026-10-22 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 2✓ — Verified: CONTRACT 3✓
|
LOW | 2 +2 | 3 | 100% | 1 · 1✓ | 2026-10-22 |
Recent failure clusters
-
observed PROJECT_TEST exit 101 ×1 4.6.4 os=linux clap::Arg sha256:a5ae8fd57d8b…error: test failed, to rerun pass `--test contract` · running 0 tests …rust/test · test-runner-diagnostic · outer cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-22 · Last seen: 2026-10-22
Symbols
- clap::Arg 1 1 of 1 runs passed
- clap::ArgAction
- clap::Args
- clap::Command 1 1 of 1 runs passed
- clap::CommandFactory
- clap::FromArgMatches
- clap::Parser
- clap::ValueEnum
Published samples
- clap 4.6.4 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-22