Recordscargocrypto-common0.2.2
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | |
|---|---|---|
| BlockSizeUser | 100%2 | |
| KeyExport | 100%2 | |
| KeyInit | 100%2 | |
| KeyIvInit | 100%2 | |
| OutputSizeUser | 100%2 | |
| crypto_common::Block | 100%2 | 100%7 |
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_COMPILE 4✓ 12✕ · PROJECT_PROCESS 10✓ · PROJECT_TEST 3✓
|
ELEVATED FAILURE | 29 | 0 | 59% | 1 | 2026-11-16 |
| node 22.23 · JS · cargo · linux glibc
Observations: PROJECT_COMPILE 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-11-19 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 7✓ · PROJECT_TEST 7✓ — Usage: USED 8✓ — Verified: CONTRACT 5✓
|
LOW | 14 +8 | 5 | 100% | 1 · 1✓ | 2026-11-21 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0034 ×3 0.1.7 → 0.2.2 os=linux sha256:82432d69f18b…error[E0034]: multiple applicable items in scoperust/rustc · compiler-diagnostic · outer cargo run, cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-04 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 ×2 0.2.2 os=linux sha256:22f98861a66c…error: could not compile `cipher-block-sample` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo checkEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 E0369 ×1 0.2.2 os=linux sha256:0e4f0e387ab1…error[E0369]: binary operation `==` cannot be applied to type `Result<(), StreamCipherError>`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 ×1 0.2.2 os=linux sha256:165d3075106a…error: could not compile `sample-cipher` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 E0425 ×1 0.2.2 os=linux sha256:47136e870e91…error[E0425]: cannot find type `DummyBlockSize` in this scoperust/rustc · compiler-diagnostic · outer cargo checkEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 E0277 ×1 0.2.2 os=linux sha256:cc078ff62edf…error[E0277]: the trait bound `(): BlockSizeUser` is not satisfiedrust/rustc · compiler-diagnostic · outer cargo checkEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 ×1 0.2.2 os=linux sha256:d9491066a9c3…error: could not compile `cipher-block-sample` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-09 · Last seen: 2026-11-09
-
observed PROJECT_COMPILE exit 101 ×1 0.2.2 os=linux crypto_common::BlockSizeUser sha256:007a8abdbaae…error: could not compile `scratch-crypto-common` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo buildEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-12 · Last seen: 2026-11-12
-
observed PROJECT_COMPILE exit 101 E0038 ×1 0.2.2 os=linux crypto_common::BlockSizeUser sha256:037d3de20190…error[E0038]: the trait `BlockSizeUser` is not dyn compatiblerust/rustc · compiler-diagnostic · outer cargo buildEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-12 · Last seen: 2026-11-12
-
observed PROJECT_COMPILE exit 101 E0432 ×1 0.2.2 os=linux crypto_common::typenum::U16 sha256:4ad8a126cd50…error[E0432]: unresolved import `crypto_common::BlockSizes`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-16 · Last seen: 2026-11-16
-
observed PROJECT_COMPILE exit 101 ×1 0.2.2 os=linux crypto_common::typenum::U16 sha256:79fbd2e86853…error: could not compile `sample-crypto-common-u16` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-16 · Last seen: 2026-11-16
Symbols
- BlockSizeUser 1 1 of 1 runs passed
- KeyExport 1 1 of 1 runs passed
- KeyInit 1 1 of 1 runs passed
- KeyIvInit 1 1 of 1 runs passed
- OutputSizeUser 1 1 of 1 runs passed
- SerializableState 1 1 of 1 runs passed
- SetIvState 1 1 of 1 runs passed
- TryKeyInit 1 1 of 1 runs passed
- crypto_common::AddBlockSize
- crypto_common::Block 1 1 of 1 runs passed
- crypto_common::BlockSizeUser 1
- crypto_common::InnerIvInit
- crypto_common::InnerUser
- crypto_common::InvalidKey
- crypto_common::InvalidLength
- crypto_common::Iv
- crypto_common::IvSizeUser
- crypto_common::IvState
- crypto_common::Key
- crypto_common::KeyExport
- crypto_common::KeyInit
- crypto_common::KeyIvInit
- crypto_common::KeySizeUser
- crypto_common::Output
- crypto_common::OutputSizeUser
- crypto_common::ParBlocks
- crypto_common::ParBlocksSizeUser
- crypto_common::Reset
- crypto_common::SetIvState
- crypto_common::SubBlockSize
- crypto_common::TryKeyInit
- crypto_common::array::Array
- crypto_common::hazmat::DeserializeStateError
- crypto_common::hazmat::SerializableState
- crypto_common::hazmat::SerializedState
- crypto_common::typenum::U12
- crypto_common::typenum::U16 1
- crypto_common::typenum::U17
- crypto_common::typenum::U24
- crypto_common::typenum::U32
- crypto_common::typenum::U4
- crypto_common::typenum::U64
- crypto_common::typenum::U8
- crypto_common::typenum::Unsigned
Published samples
- crypto-common 0.2.2 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-11-09